canonical: https://jentic.com/apis/akamai.com/akamai # Akamai SIEM API Jentic publishes the only available OpenAPI specification for Akamai SIEM API, keeping it validated and agent-ready. The Akamai SIEM API exposes a security information and event management integration surface - three endpoints covering token-based authentication and resource listing and retrieval. It is intended for ingesting Akamai security events into an external SIEM, with API-key authentication on the X-API-Key header and a separate token endpoint for issuing access tokens. ## For AI agents Issue an access token and pull security resources from Akamai for ingestion into a SIEM pipeline. ## Scope Does not configure WAF rules, manage CDN properties, or stream raw HTTP logs - use for SIEM token issuance and security resource lookups only. ## Capabilities - Issue an access token via the auth endpoint for downstream calls - List the security resources exposed by the SIEM integration - Retrieve the details of a specific resource by id - Authenticate every call with an X-API-Key header - Wire Akamai security events into an external SIEM or analytics pipeline ## Use cases ### SIEM event ingestion bootstrap Stand up a pipeline that ingests Akamai security events into a SIEM. The agent calls /auth/token to obtain an access token, then iterates /resources to discover what is available, fetching each resource by id for downstream forwarding. Example prompt: POST /auth/token, then GET /resources and GET /resources/{id} for each resource to forward to the SIEM ### Periodic security resource sync Run a scheduled job that polls Akamai for new or updated security resources and synchronises them into a downstream tracker. The agent compares the latest resource list against the local cache and pulls only changed entries. Example prompt: GET /resources, diff against the previous run's ids, and call GET /resources/{id} for each new or changed entry ### AI agent integration via Jentic A security agent uses Jentic to discover and call the Akamai SIEM operations by intent. The X-API-Key stays in your Jentic One instance, the agent loads the operation schema at runtime, and the agent's prompt never contains the credential. Example prompt: Search Jentic for 'pull Akamai security resources', load the Akamai GET /resources operation, and execute it ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /auth/token | Get access token | | GET | /resources | List security resources | | GET | /resources/{id} | Get a resource by id | ## Key resources - **Authentication** — Issue an access token via the /auth/token endpoint - **Resources** — List and retrieve security resources for SIEM ingestion ## Why Jentic - **Setup:** Wiring Akamai SIEM by hand means sending its X-API-Key, issuing an access token at /auth/token, and writing your own retry logic. Through Jentic you install once, import Akamai SIEM from the API Directory, store the key once, and your agent calls it while Jentic handles the token step. - **Permission scoping:** Akamai SIEM reads security resources through /resources and /resources/{id} and issues tokens by request body, so scope your agent by operation: limit it to the operations it needs, such as listing security resources, and leave out token issuance it does not use. - **Credential handling:** Your Akamai X-API-Key and access token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'pull Akamai security resources', and Jentic returns the matching SIEM operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Splunk** — Common downstream destination for Akamai SIEM events. - **Elastic / Kibana** — Alternative SIEM and analytics destination for Akamai events. - **Cloudflare** — Edge security and CDN platform with its own logs and event APIs. ## FAQ ### Why is there no official OpenAPI spec for Akamai SIEM API? Akamai does not publish an OpenAPI specification for this SIEM integration. Jentic generates and maintains this spec so that AI agents and developers can call Akamai SIEM API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Akamai SIEM API use? The API requires an API key in the X-API-Key header on every call, and exposes POST /auth/token for issuing a separate access token used in subsequent requests. Through Jentic, both credentials sit in the encrypted Jentic One instance. ### What resources can I retrieve from the SIEM API? GET /resources returns the list of security resources exposed by the integration, and GET /resources/{id} returns the full details for one. The endpoint surface is intentionally small - three operations focused on token issuance and resource pulls. ### How do I forward Akamai events into Splunk through Jentic? Use the Jentic search query 'pull Akamai security resources'. Jentic returns the GET /resources and GET /resources/{id} operations; chain those calls and forward the responses to your Splunk HEC endpoint. ### Are there rate limits on the Akamai SIEM API? Rate limits are not declared in this OpenAPI spec; Akamai applies account-level quotas. Treat polling on a per-minute schedule as a safe default and back off on 429 responses. ### Can I limit what my agent is allowed to do with the Akamai SIEM API? Yes. Because Jentic One is self-hosted, you set the rules that decide which Akamai SIEM operations your agent may call and which credentials it may use. You can scope the agent to only the operations it needs, such as listing security resources with GET /resources and retrieving one with GET /resources/{id}, while excluding token issuance at POST /auth/token if the agent does not need it. Your X-API-Key and access token are injected at execution time and never enter the agent's prompt or logs.