Skip to main content

​
Base URLs

EnvironmentBase URL
Productionhttps://crypto-api.yativo.com/api/
Sandboxhttps://crypto-sandbox.yativo.com/api/
The sandbox environment is fully functional for testing. All endpoint pages in this reference include a live API playground connected to the sandbox so you can make real test calls directly from the docs.

​
Authentication

Yativo Crypto supports two authentication methods depending on the context.

​
Bearer Token (Session Auth)

Obtained by calling the Login or Register endpoints. Include it in every request: 
Authorization: Bearer YOUR_ACCESS_TOKEN
Access tokens are short-lived. Use the Refresh Token endpoint to obtain a new one when it expires.

​
API Key Auth

For server-to-server integrations, create an API key via the Create API Key endpoint. Pass the key in the header: 
X-API-Key: YOUR_API_KEY
Some sensitive operations (creating or revoking API keys) additionally require a two-factor token passed as: 
X-2FA-Token: YOUR_2FA_TOKEN

​
Common Headers

HeaderRequiredDescription
AuthorizationYes (session auth)Bearer YOUR_ACCESS_TOKEN
X-API-KeyYes (API key auth)Your API key
Content-TypeYes (POST/PUT)application/json
X-2FA-TokenConditionalRequired for API key management
Idempotency-KeyOptionalPrevent duplicate transactions

​
Content Type

All request bodies must be sent as JSON with the Content-Type: application/json header.

​
Response Format

Every response follows this structure: 
{
  "status": "success",
  "message": "Human-readable message",
  "data": { ... }
}
Error responses follow the same shape with "status": "error" and relevant HTTP status codes (400, 401, 403, 404, 422, 429, 500).

​
Further Reading