Account API keys are best for backend services that need to make requests on behalf of a specific user without managing session tokens. They are long-lived and don’t expire unless revoked.
Store account API keys securely on your server. Never expose them to clients.
Create an account API key
This is called from your backend using the project API key.
The secret_key is only shown once. Store it securely immediately after creation.
Use the API key
Pass the secret key in the X-API-KEY header for all account and wallet requests.
List API keys
Retrieve all API keys for an account. Note that secret keys are not returned — only public keys and metadata.
Delete an API key
Permanently revoke an API key. This cannot be undone.
Available routes
All routes under /api/v1/account/* and /api/v1/wallet/* accept account API keys — the same routes that accept session tokens.
Comparison with session tokens