Skip to main content
GET
/
api-keys
List API keys
curl --request GET \
  --url https://api.dialnexa.com/v1/api-keys \
  --header 'Authorization: Bearer <token>'
{
  "data": [
    {
      "id": "YOUR_API_KEY",
      "name": "Production Server",
      "last_used_at": "2024-03-10T08:00:00.000Z",
      "is_expired": false,
      "created_at": "2024-03-01T10:00:00.000Z"
    }
  ]
}
Returns every API key registered on your workspace, paginated. Each entry includes the key’s stable id, its display name, the creation timestamp, and the last_used_at timestamp updated each time a request is authenticated with the key. Secret values are never returned by any endpoint after key creation, if you have lost a secret, revoke the key with Revoke API Key and issue a new one with Create API Key.

​
When to use this

  • Security audits: enumerate every key, check last_used_at to find dormant keys that should be revoked.
  • Rotation playbooks: confirm a newly created key is present before deploying it to consumer services.
  • Operational dashboards: render an API key management page with the canonical list.
  • Compliance reviews: produce a report of which keys exist in each workspace.
For details on how to rotate keys safely, see Key rotation.

​
Query parameters

ParameterDescription
pagePage number, starting from 1.
limitResults per page (max 100, default 20).
searchFilter by name (partial match).

​
Errors

  • 403 Forbidden is returned when the caller’s API key cannot manage other keys.

​
Request

curl "https://api.dialnexa.com/v1/api-keys" \
  -H "Authorization: Bearer YOUR_API_KEY"

​
Response

{
  "data": [
    {
      "id": "abcgvvzzlrbnqy",
      "name": "Production Server",
      "created_at": "2024-03-01T10:00:00.000Z",
      "last_used_at": "2024-05-13T18:00:00.000Z"
    }
  ],
  "meta": { "page": 1, "limit": 20, "total": 1 }
}

Authorizations

​
Authorization
string
header
required

Pass your API key as a Bearer token in the Authorization header.

Response

200 - application/json

Success.

​
data
object[]