# List organization API keys

`GET /organizations/{org_id}/api_keys`

Retrieves the API keys for the specified organization. The response does not include API key tokens. A token is only provided when creating an API key. API keys can also be managed in the Neon Console. For more information, see [Manage API keys](/guides/manage-operate-manage-api-keys).

[Markdown for AI context](/guides/apis-sdks-reference-api-organizations-list-org-api-keys)

```bash title="REST API - curl"
curl "https://console.neon.tech/api/v2/organizations/$ORG_ID/api_keys" \
  -H "Authorization: Bearer $NEON_API_KEY"
```

Every field below is optional. An empty body works too.

Also available in

::::tabs
:::tab{title="CLI"}
```bash
neon api-keys list
```
:::

:::tab{title="SDK"}
:::

:::tab{title="Console"}
Console path: Organization → Settings → API keys
:::
::::

## Parameters

Organization

`org_id`

string

The Neon organization ID

## Response

200

Returned the API keys for the specified organization

::::tabs
:::tab{title="schema"}
Depth
:::

:::tab{title="example"}
:::
::::

No schema available.

## Errors

default

General error

This endpoint can return the standard Neon API error response.

Response fields

- `message` Required. Human-readable error message.
- `code` Required. Machine-readable error code.
- `request_id` Optional. Request identifier for debugging. You can provide one with the `X-Request-ID` header.

Retry guidance

If no response is returned, the request may still have reached the server. This is why retry safety depends on the method and status code.

Idempotent methods (`GET`, `HEAD`, `OPTIONS`) are generally safe to retry after a network error or timeout. Non-idempotent methods (`POST`, `PATCH`, `DELETE`, `PUT`) can change state, so avoid automatic retries unless your workflow can tolerate duplicate effects.

Responses with `423 Locked` or `503 Service Unavailable` are safe to retry. `423 Locked` means the resource is temporarily locked, usually because another operation is in progress.

## Related pages

- [Assign or update VPC endpoint](./apis-sdks-reference-api-organizations-assign-organization-vpc-endpoint.md)
- [Create organization API key](./apis-sdks-reference-api-organizations-create-org-api-key.md)
- [Create organization invitations](./apis-sdks-reference-api-organizations-create-organization-invitations.md)
- [Delete VPC endpoint](./apis-sdks-reference-api-organizations-delete-organization-vpc-endpoint.md)
- [List organization invitations](./apis-sdks-reference-api-organizations-get-organization-invitations.md)
- [List organization members](./apis-sdks-reference-api-organizations-get-organization-members.md)
- [List VPC endpoints](./apis-sdks-reference-api-organizations-list-organization-vpc-endpoints.md)
- [List VPC endpoints across all regions](./apis-sdks-reference-api-organizations-list-organization-vpc-endpoints-all-regions.md)
- [Remove organization member](./apis-sdks-reference-api-organizations-remove-organization-member.md)
- [Remove organization spending limit](./apis-sdks-reference-api-organizations-delete-organization-spending-limit.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.