API Documentation

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.

You have to pass the API keys with each request in the HTTP headers as X-API-ID (public) and X-API-KEY (private) parameters. Or pass an OAuth token with each request in the headers as Authorization: Bearer {token} parameter.

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.

Log in 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.