GET /v1/api_keys - SEC API for AI

curl -X GET \
  -H "Authorization: Bearer $SECAPI_BEARER_TOKEN" \
  -H "secapi-version: 2026-03-19" \
  "https://api.secapi.ai/v1/api_keys"

{
  "requestId": "req_2ZK8Q1W9F4M6P7R3"
}

List API keys for the current organization

Audience: application and coding agent.

Canonical metadata

requestId
traceparent

Example request

curl -X GET \
  -H "Authorization: Bearer $SECAPI_BEARER_TOKEN" \
  -H "secapi-version: 2026-03-19" \
  "https://api.secapi.ai/v1/api_keys"

POST /v1/api_keys is a dashboard/control-plane operation. Use a WorkOS browser-session bearer token with api_keys:manage permission to create the key. After creation, use the returned secret as the x-api-key header for REST, SDK, CLI, and server-to-server MCP requests. The secret is revealed exactly once; later list responses return metadata and prefix only.

Example response

{
  "requestId": "req_2ZK8Q1W9F4M6P7R3"
}

Give this prompt to your agent

Failure posture

treat non-2xx responses as contract-aware failures, not free-form errors
preserve requestId and traceparent in logs and downstream reports
if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff

POST /mcp POST /v1/api_keys

​Canonical metadata

​Example request

​Example response

​Give this prompt to your agent

​Failure posture

Canonical metadata

Example request

Example response

Give this prompt to your agent

Failure posture