Skip to main content
A user API key lets you use the Arize AX APIs, SDKs, MCP server, and skills programmatically, and you need one to send traces. The key is tied to your user, so it stops working if you are removed from the account. For shared pipelines and integrations, a service key is a better fit.

Create an API key

  1. Go to Settings → Account Settings → API Keys and select User API Keys.
  2. Click New API Key.
  3. Enter a key name.
  4. Set an expiration date if you want. The default is no expiration. Accounts with a key lifetime limit cannot set a date past that limit.
  5. Click Create Key and copy the key. The key is shown only once.
Create API Key dialog with a Key Name field, a note that user keys are disabled when you are removed from the account, and an Expiration date set to Never

The Create API Key dialog, with the key name and expiration date.

Creating a key requires developer access. See Developer access.

Refresh an API key

Refreshing a key through the REST API gives you a new key with the same name and description and revokes the old one. If you need time to update the systems that use it, pass a grace period and the old key stays valid for that many seconds. The new key cannot expire later than the original. You can refresh keys you created, and account admins can refresh any key.

Revoke an API key

Revoke API key is in the key’s menu. A revoked key stops working immediately.
The developer access lock under Account Settings → Security stops users from creating or refreshing API keys. It also blocks user keys from the REST and GraphQL APIs. Service keys keep working.