API Information

API Reference

The Quant-trading.network API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

Each trading algorithm has its own resource URL, but its nested resources, requests, responses, and verbs are predictable and structurally the same.

Just getting started?

Check out our interactive API explorer and documentation.

API base URL?


Official client libraries?

Python client library on GitHub.

Not a developer?

Please have a look into our working example trading bot on GitHub for BitMEX.


The Quant-trading.network API uses API keys to authenticate requests. You can view and manage your API keys in the Account Dashboard.

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth. If your API key was compromised and someone else is using it illegitimately, this will have disastrous consequences because our algorithms are only executed once for a given interval of time.

All requests will need to have an HTTP header X-API-KEY with the provided API key as for example -H "X-API-KEY: +1l2rmhZVEUa4IooMsLPUn1Zqava6MCA7xjV6SZWHjc=". If you do not include your key when making an API request, or use one that is incorrect or outdated, the Quant-trading.network API returns an error.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.

Rate limits

Requests to our REST API are rate limited to 20 requests per 1 minute. This counter refills continuously.

On each request to the API, these headers are returned:


Use these headers to determine your current limit and remaining requests. At the UNIX timestamp designated by X-RATELIMIT-RESET, you will have the rate limit counter completely reset to retry your current request.

If you are limited, you will receive a 429 response. In this situation sleep enough time until you will have enough requests to proceed.

Additionally, each response of trading algorithm execution will include the field millisecondsToNextDecision which will contain the number of milliseconds until the next algorithm execution is available. Also, each algorithm has its own parameters which you can get and know exactly how many seconds is the algorithm polling interval. This information is included in the field decisionPollingIntervalInSeconds.