All Open API requests don't require authentication. All non-open API requests must be provided with unique API keys, which you can generate in settings or with an OAuth token.

Currency pair's (ticker's) base and quote were reversed (changed places) in API v2, compared to API v1. What was MINTME/token (base=mintme, quote=token) became token/MINTME (base=token, quote=mintme), what was BTC/MINTME, became MINTME/BTC.

Send both X-API-ID (public) and X-API-KEY (secret) in the HTTP headers for every request that reads private account data or changes your account. This includes wallet balances, deposit addresses, wallet history, personal orders and the WebSocket hash. Clients that previously sent only X-API-ID for these requests must now also send X-API-KEY. Requests with a missing, wrong or revoked key are rejected. Market data endpoints that use API key authentication also require both headers. You can also use a supported OAuth access token in the Authorization: Bearer {token} header. Public endpoints do not require credentials.

You can get the OAuth token by sending a grant request to the OAuth API address: /oauth/v2/token?client_id={YOUR_CLIENT_ID}&grant_type=client_credentials&client_secret={YOUR_SECRET}. The token will expire after some time, you should get a new token again after expiration.

Our data is delivered to you on-demand, using well-documented and simple HTTP RESTful API in JSON format. Requests to the API are limited to 5 per second with bursts not exceeding 10 requests. All the requests above this limit won't be processed and the API will return 503 HTTP code. To avoid exceeding the limit, it's recommended to implement a caching mechanism in your application.

to generate your own API keys or an OAuth Client ID and Secret.

You can test our API here. Authorize with your generated keys or token and click on specific methods to see how they work live.