Atomically revoke an existing API key and issue a replacement with the same
metadata (name, description, and key type). Attempting to refresh a key
you did not create returns a 400 error.
The old key is invalidated and the new key is activated in a single transaction —
there is no window where neither key is valid. The full new key value (key) is
only returned once in the response. Store it securely.
Expiry behaviour: Supply expires_at in the request body to set an expiration
on the replacement key. Omit expires_at (or send an empty body {}) to create
the replacement key with no expiration (infinite lifetime).
Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format
The unique identifier of the API key A universally unique identifier
"RW50aXR5OjEyMzQ1"
Optional body for overriding expiry on a refreshed API key.
Expiration timestamp for the refreshed key. If omitted, the refreshed key has no expiration (infinite lifetime).
"2027-01-01T00:00:00Z"
API key successfully created or refreshed. The raw key is only returned once.
Unique identifier for the API key.
User-defined name for the API key.
Type of the API key.
user, service Current status of the API key.
active, deleted Redacted version of the key suitable for display (e.g., "ak-abc...xyz").
Timestamp when the key was created.
ID of the user who created the key.
The full API key value. Only returned once at creation or refresh time. Store it securely — it cannot be retrieved again.
Optional user-defined description for the API key.
Optional timestamp when the key will expire.