> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/api_keys

> List API keys for the current organization

List API keys for the current organization

<Info>
  Audience: application and coding agent.
</Info>

## Canonical metadata

* `requestId`
* `traceparent`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X GET \
    -H "Authorization: Bearer $SECAPI_BEARER_TOKEN" \
    -H "secapi-version: 2026-03-19" \
    "https://api.secapi.ai/v1/api_keys"
  ```
</RequestExample>

<Info>
  `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.
</Info>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/api\_keys to list API keys for the current organization. Preserve `requestId`, `traceparent` in the output. Return a concise markdown summary plus the exact structured payload fields that a downstream engineer or agent should keep using this result.
</Prompt>

## 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