Zernio
Zernio
API Reference

API Keys

List keysGETCreate keyPOSTDelete keyDELETEVerify credentialGET
Dashboard
llms.txtOpenAPI
OverviewPlatformsAPI ReferenceResources
API Keys

List keys

Returns all API keys for the authenticated user. Keys are returned with a preview only, not the full key value.

GET
/v1/api-keys

Authorization

bearerAuth
AuthorizationBearer <token>

API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.

In: header

Response Body

application/json

application/json

application/json

{  "apiKeys": [    {      "id": "6507a1b2c3d4e5f6a7b8c9d0",      "name": "Production API Key",      "keyPreview": "sk_12345678...abcdef01",      "expiresAt": "2025-12-31T23:59:59Z",      "createdAt": "2024-01-15T10:30:00Z",      "scope": "full",      "profileIds": [],      "permission": "read-write"    },    {      "id": "6507a1b2c3d4e5f6a7b8c9d1",      "name": "Analytics Read-Only",      "keyPreview": "sk_87654321...12345678",      "expiresAt": null,      "createdAt": "2024-03-20T14:45:00Z",      "scope": "profiles",      "profileIds": [        {          "_id": "6507a1b2c3d4e5f6a7b8c9d0",          "name": "Main Brand",          "color": "#ffeda0"        }      ],      "permission": "read"    }  ]}
Was this page helpful?

Check a verification code

Verify the code the user typed. Wrong, expired, and exhausted codes answer 200 with `valid: false` and the settled `status`. Only an unknown id is a 404. A correct code consumes the verification (single-use, `status: approved`) and fires the `verification.approved` webhook; the 5th wrong attempt settles it as `max_attempts_reached` and fires `verification.failed`.

Create key

Creates a new API key with an optional expiry. The full key value is only returned once in the response.