---
title: "List Endpoint API Keys"
method: GET
path: "/v2.0/endpoints/{endpointId}/apikeys"
tags: ["Endpoints"]
---

# List Endpoint API Keys

`GET /v2.0/endpoints/{endpointId}/apikeys`

Lists all API keys configured on the given Webhook/Generic Endpoint. The response never contains the SHA-256 hash or the plaintext key — only the masked preview, name, id, and creation timestamp.

## Path parameters

- `endpointId` string, required

## Headers

- `Accept` 'application/json' | 'application/hal+json' | 'application/xml' | 'text/xml' | 'text/csv'

## Response `200`

Array of Endpoint API Keys (metadata only).

- object[] — Array of Endpoint API Keys for the given endpoint.
  - `_id` string
  - `name` string — Customer-provided display name for the key.
  - `keyPreview` string — Masked preview of the plaintext key (first 4 chars + masked middle + last 4 chars). Captured at generation time.
  - `createdAt` integer — Unix-timestamp

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `402` — Upgrade your Plan to increase your Quota.
- `403` — The user lacks permission to read this Endpoint.
- `404` — Endpoint not found.
- `405` — The method received in the request-line is known by the origin server but not supported by the target resource.
- `409` — The request conflicts with current state of the server.
- `413` — The request entity is larger than limits defined by server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `501` — The server does not support the functionality required to fulfill the request.
- `502` — The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
- `503` — The server is not ready to handle the request.
- `504` — The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

---

[API](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference.md) · [All operations](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cognigy/simulator-openapi-rest-ful-api-reference/revisions/85b2872bdfb7/schema)