API Keys API

These endpoints let you manage your account's API keys from code. They all operate on the calling account's own keys only.

API Keys API These endpoints let you manage your account's API keys from code. They all operate on the calling account's own keys only. There are two kinds of key, and they live on separate paths: Your main key — the single full-access key under Settings → Integrations → API Key . Look up its masked preview, check your rate-limit usage, rotate it, or revoke it. These are the /api-keys/current , /api-keys/rotate and /api-keys/usage endpoints below. Scoped keys — extra, named keys you create for a specific job, each limited to the parts of the API you choose. These are the /api-keys and /api-keys/{id} endpoints under Scoped keys . Nothing about your main key changes when you create one; existing integrations carry on untouched. All paths below are relative to the API base URL: https://api.relaytiv.com/v1 Every request must be authenticated. See Authentication for the four accepted methods. The examples here use the X-API-Key header (and one query-parameter form for cURL). Read this first. Rotating or revoking your key takes effect immediately . The moment either call succeeds, the old key stops working — every integration that still uses it starts getting 401 errors. Plan for it: rotate during a maintenance window and update all your integrations right away. Get current key metadata Returns your active key: the full key in api_key when a retrievable copy exists, a masked preview (first 4 and last 4 characters), and, when available, the date it was created. api_key is null for k