Akamai API icon

Akamai API

Interact with Akamai APIs

Actions5

DELETE Request

AI-generated

Overview

This node allows users to interact with Akamai APIs by making HTTP requests authenticated via Akamai EdgeGrid. Specifically, the "DELETE Request" operation enables sending DELETE requests to any specified Akamai API endpoint path. This is useful for scenarios where you need to remove or delete resources managed by Akamai services, such as deleting user profiles, configurations, or other entities exposed by Akamai's APIs.

Practical examples include:

  • Deleting a user profile from Akamai Identity Management.
  • Removing an edge configuration or cache invalidation rule.
  • Cleaning up obsolete resources programmatically via automation workflows.

The node supports customization of query parameters, headers, and response handling, making it flexible for various API requirements.

Properties

Name Meaning
API Path The specific API endpoint path to send the DELETE request to. Must start with a slash ("/"). Example: /identity-management/v3/user-profile.
PAPI Use Prefixes Controls whether to override the client's default setting for ID prefixes in responses (such as prp_, ctr_, grp_). Options:
- Don't Send Header
- Include Prefixes (True)
- Remove Prefixes (False)
Return Full Response If enabled, returns the full response object including metadata (meta) and data (data), instead of just the response body. Useful for debugging or when response headers/status are needed.
Options Additional options to customize the request:
• Query Parameters: Key-value pairs appended to the URL.
• Headers: Custom HTTP headers to include in the request.

Output

The node outputs JSON data representing the response from the Akamai API:

  • By default, the output contains the parsed JSON response body returned by the DELETE request.
  • If "Return Full Response" is enabled, the output is an object with two fields:
    • meta: Contains metadata about the response such as HTTP status code, endpoint called, and response headers.
    • data: Contains the actual response body data.

The output is paired with the input item index for traceability.

No binary data output is produced by this node.

Dependencies

  • Requires an Akamai API authentication credential configured in n8n with the necessary tokens (client token, client secret, access token) and host URL.
  • Uses the akamai-edgegrid npm package internally to handle authentication and request signing.
  • The node expects the Akamai API host URL to be properly set in the credentials.
  • No additional environment variables are required beyond the credential setup.

Troubleshooting

  • Common issues:

    • Invalid or missing credentials will cause authentication failures.
    • Incorrect API path formatting (missing leading slash) may result in request errors.
    • Malformed query parameters or headers can cause unexpected API errors.
    • Parsing errors if the API returns non-JSON responses or error messages.

  • Error messages:

    • Errors related to failed authentication typically indicate invalid or expired API tokens.
    • "Failed to parse response" errors occur if the response body is not valid JSON; check the API endpoint and response format.
    • HTTP status codes and error details are included in the output when "Return Full Response" is enabled, aiding diagnosis.

  • Resolution tips:

    • Verify that the API path is correct and starts with "/".
    • Ensure the API credentials are correctly configured and have sufficient permissions.
    • Use the "Return Full Response" option to get detailed error information.
    • Check network connectivity and Akamai service status if requests fail unexpectedly.

Links and References

Discussion