Skip to main content
API keys let your server authenticate with Yativo without requiring a logged-in user session. They support fine-grained permission scopes and can be rotated or revoked at any time.
2FA must be enabled on your account before you can create API keys. All key management operations require a valid TOTP code in the X-2FA-Token header.

Permissions

When creating an API key, you specify which operations it is allowed to perform: Assign only the permissions your integration actually needs.

Create an API Key

POST /apikey/create Requires the X-2FA-Token header with a current TOTP code.
string
required
Current 6-digit TOTP code from your authenticator app.
string
required
Human-readable name to identify this key.
array
required
Array of permission strings. One or more of: read, write, transactions, webhooks.
number
Number of days until the key expires. Omit for a key that does not expire.
cURL
Response
The api_secret is only returned once at creation. Store it securely in your secrets manager immediately. It cannot be retrieved again.

List API Keys

GET /apikey/list Returns all API keys on your account (secrets are not included in list responses).
cURL
Response

Get API Key

GET /apikey/{id}
cURL

Revoke an API Key

POST /apikey/{id}/revoke Permanently deactivates the key. This cannot be undone.
string
required
Current 6-digit TOTP code.
cURL

Rotate an API Key

POST /apikey/{id}/rotate Generates a new api_secret and invalidates the old one. Use this to rotate credentials without deleting and recreating the key.
string
required
Current 6-digit TOTP code.
cURL
Response

Update Permissions

PUT /apikey/{id}/permissions
string
required
Current 6-digit TOTP code.
array
required
New set of permissions. This replaces the existing permission set entirely.
cURL

Exchange for Bearer Token

POST /apikey/token For server-to-server calls, you can exchange your API key and secret for a short-lived Bearer token. This is useful when the downstream service expects a standard Authorization: Bearer header.
string
required
Your API key (yvk_live_...).
string
required
Your API secret (yvs_live_...).
cURL
Response

Authentication Methods Summary

Pass your key and secret as headers on every request. No token management required.
Store API keys in environment variables or a secrets manager. Never hardcode them in source code or commit them to version control.