---
title: Akamai
slug: connectors/akamai
docTags: 
createdAt: 2026-06-09T16:30:32.471Z
---

The Akamai connector enables users to programmatically interact with Akamai's services through custom HTTP requests, facilitating advanced content delivery management and network insights.

Akamai is a global content delivery network (CDN), cybersecurity, and cloud service company that ensures fast, reliable, and secure online experiences. The Akamai connector for Swimlane Turbine allows users to construct and dispatch custom HTTP requests to Akamai's API, enabling direct interaction with Akamai services. This integration empowers security teams to automate their workflows, manage content delivery, and enhance their cyber defense mechanisms by leveraging Akamai's advanced edge security solutions. With the ability to automate actions such as cache purging, security configuration, and real-time data analysis, users can respond swiftly to threats and optimize web performance without manual intervention.

## Prerequisites

To effectively utilize the Akamai connector within Swimlane Turbine, ensure you have the following prerequisites:

- Edge Grid Authentication with the following parameters:
  - URL: The endpoint URL for the Akamai API service.
  - Client Token: Your unique client token provided by Akamai for API access.
  - Access Token: A specific token granting permissions to perform actions via the API.
  - Client Secret: A confidential key used in conjunction with the tokens for secure authentication.

## Capabilities

Because the connector allows for any generic action to be manually built, it supports all possible endpoints and actions Akamai provides.

## Additional Documentation

- [Akamai Connector Documentation](https://docs.swimlane.com/connectors/akamai)
- [Akamai API Documentation](https://techdocs.akamai.com/home/page/apis-overview)
- [Akamai Authentication Guide](https://docs.swimlane.com/authentication-guides/akamai)

# Configurations

## Edge Grid Authentication

Authenticates using Edge Grid Auth

### Configuration Parameters

| **Parameter**  | **Description**                                       | **Type** | **Required** |
| -------------- | ----------------------------------------------------- | -------- | ------------ |
| url            | Unique string followed by `xxxx.luna.akamaiapis.net`. | string   | Required     |
| client\_token  | The value of the client\_token from the .edgerc file. | string   | Required     |
| access\_token  | The value of the access\_token from the .edgerc file. | string   | Required     |
| client\_secret | Client Secret                                         | string   | Required     |
| verify\_ssl    | Verify SSL certificate                                | boolean  | Optional     |
| http\_proxy    | A proxy to route requests through.                    | string   | Optional     |

# Actions

## Send HTTP Request to Akamai

Build and send a custom HTTP request to Akamai, allowing for flexible interactions with the service's API.

### Input

| **Argument Name** | **Type** | **Required** | **Description**                                                                                     |
| ----------------- | -------- | ------------ | --------------------------------------------------------------------------------------------------- |
| `endpoint`        | string   | Optional     | Path to the endpoint after url in asset. Use double brackets with path parameters for dynamic URLs. |
| `method`          | string   | Optional     | Method of the request such as: POST, GET, PUT, PATCH, DELETE. (Note, others are available to use)   |
| `data_body`       | object   | Optional     | Body to send as data, this allows you to set the content-type in the headers manually.              |
| `headers`         | object   | Optional     | Request headers to send with the individual request.                                                |

### Input Example

`{"endpoint":"api/v3/users"}`

### Output

| **Parameter**   | **Type** | **Description**                                                              |
| --------------- | -------- | ---------------------------------------------------------------------------- |
| `status_code`   | number   | The HTTP response status code                                                |
| `data`          | object   | The JSON response body                                                       |
| `response_text` | string   | Output field: response\_text                                                 |
| `reason`        | string   | The HTTP reason, often times an error message can be here. OK means success. |

### Output Example

`{"response_text":"string"}`

# Response Headers

| **Header**   | **Description**                                       | **Example**                   |
| ------------ | ----------------------------------------------------- | ----------------------------- |
| Content-Type | The media type of the resource                        | application/json              |
| Date         | The date and time at which the message was originated | Thu, 01 Jan 2024 00:00:00 GMT |