Crypto.com Exchange API Order Rules for a Trading Bot (2026): No Stop Orders for Retail Keys, Tick Sizes, Fees Taken From the Coin, Rate Limits and the IP Allow-List

The Crypto.com Exchange API is fast and strict: tight per-100-millisecond rate limits, a 60-second clock tolerance on every signed request, an IP allow-list on the key, and, in JorgAI's experience, stop and stop-limit orders that the API refuses for retail keys. This page lists the rules as JorgAI's integration applies them, verified from the integration code on November 6, 2026, with the limits the Exchange's developer documentation published when the integration was built. For the same rows across all six connected brokers, see the broker API capabilities page.

The rules in one table

What the rules mean for a bot

No stop orders at the exchange

The Exchange lists stop-loss and stop-limit order types, but a retail API key gets API_DISABLED when it tries to place one, so the protective exit cannot live at the exchange. JorgAI's monitor holds every stop and target and sends a limit a tenth of a percent under the price when a level is hit, re-sent at market if it misses. What happens if the connection drops is the outage case to read before relying on that.

The fee comes out of the coin

The Exchange takes its taker fee from the asset you bought, so a market buy of 0.1 of a coin leaves slightly less than 0.1 in the account. JorgAI sizes market buys in dollars with a quarter-percent cushion and clamps every sell to the balance actually held, floored to the tick size, so a sell never asks for more than exists.

Clocks, nonces and the allow-list

Every signed request carries a nonce that must be within 60 seconds of the exchange's clock, and the key can be bound to an IP allow-list. JorgAI signs from a fixed outbound address, which is why the setup asks you to add that address to the key. A key created without the allow-list still works; one created with the wrong address does not.

The App is not the Exchange

The Crypto.com App has no trading API. A bot trades the Exchange, which is a separate account with its own balances. Which one a bot can trade, and how to move coins between them, has its own page.

Quick answers

Can a bot place stop-loss orders on the Crypto.com Exchange?

Not with a retail API key in JorgAI's experience; the API answers API_DISABLED. The stop is held by the software and sent as a limit or market order when hit.

What is the Crypto.com Exchange API rate limit?

Per the documentation at the time the integration was built: 15 order creates or cancels per 100 milliseconds, 30 order reads per 100 milliseconds and one trade-history call a second, plus user-level limits. Check the developer documentation for the current table.

Does the Crypto.com Exchange API key need an IP allow-list?

It is optional on the key; JorgAI's setup uses it and gives you the address to add.

Is there a sandbox?

A developer UAT environment exists; members practice on JorgAI's demo simulator rather than a sandbox key.

How we put this together. The JorgAI column is a line-by-line read of the Crypto.com adapter and auto-trader workers on November 6, 2026. The Exchange column is from the developer documentation as recorded when the integration was built and from the API's own responses; the live documentation site renders in the browser only, so figures are marked with their date. For setup, how to automate crypto trading on the Crypto.com Exchange; for the head-to-head with Kraken, Kraken vs Crypto.com for automated trading; for the platforms that connect, the Crypto.com bots comparison.

To see a crypto rule run before you create a key, start on the free plan.

The figures in this article describe broker API behaviour and are not a prediction or a recommendation to buy or sell any security or digital asset. JorgAI is software that carries out the rules you set in your own brokerage or exchange account; it is not an investment adviser. Trading involves risk of loss.