Crypto.com command reference

Autoview · Reference

This is the full reference for writing Crypto.com spot orders from an Autoview alert. It goes parameter by parameter and order type by order type, and for each order type it shows the exact order Crypto.com resolves, not just the command you type. If you want the short version, the Crypto.com cheat sheet has a copy-ready line for each order type. This page is the one you keep open when you need the detail behind those lines.

Every command here was emitted by our command builder, round-tripped through the same parser the trading engine uses, and resolved through the live Crypto.com zone. The core order types (market, limit, IOC, FOK, and cancel) were also placed on a live spot account at minimum size. The resolved-order fields you see are the values the engine built. Nothing is hand-typed or assumed.

How Autoview reads a command

A command is a single line of key=value tokens separated by spaces. e=CRYPTO s=BTC_USD b=sell t=market q=0.0001 is five tokens. The order you write them in does not matter.

• First occurrence wins. If a key appears twice, Autoview keeps the first and ignores the rest. Write each key once.
• A line starting with // is a comment and places nothing. Useful for labelling an alert without triggering a trade.
• You can send several commands at once by separating them with a new line or a pipe (|). Each is parsed on its own.
• A token that starts with a colon is ignored. TradingView sometimes inserts placeholder tokens like :plot_0=; Autoview skips anything with a leading colon so those never affect the order.

Three tokens matter for every Crypto.com order: s= (the pair), b= (the side), and q= (the size). The size is not optional in practice. Read the sizing section before you send a real order.

The parameter table

These are the parameters Crypto.com spot reads. The cheat sheet uses a handful of them; this is the full set, grouped by what they do.

Routing and identity

Direction and size

Order type and price

Cancelling and closing

Order types and what each resolves to

Here is each order type with the command on the left and the order Crypto.com actually built on the right. The resolved side is the useful part: it shows that t=ioc becomes a Limit order with an immediate-or-cancel time-in-force, that a trigger turns a market order into a Stop-Loss, and so on.

One thing surprises people. Fill-or-kill and immediate-or-cancel are not separate order types on Crypto.com; they are limit orders with a different time-in-force, which is why both resolve to a Limit. A stop is the same idea from the other direction: a market or limit order with a trigger price attached, so t=market fpx=95000 is the stop, not a t=stop you might expect.

Absolute and relative prices

Every price parameter comes in two forms, and the difference is one letter.

• With the f prefix, the number is absolute. fp=100000 means the price 100000.
• Without the f, the number is an offset from a reference you supply with price=. p=-50 means fifty below the reference.

Relative pricing is the usual TradingView pattern, because the alert can hand Autoview the candle that fired it:

e=CRYPTO s=BTC_USD b=sell t=limit price={{close}} p=-50 q=0.0001

price={{close}} passes the candle close, and p=-50 rests the limit fifty below it. The same swap works for a trigger: px= is the relative form of fpx=. Because Crypto.com trades around the clock, the live price is always available, so absolute and relative prices both resolve at any hour.

Sizing: base units and percent

q= sets the size, and it reads two ways.

• A plain number is base units. q=0.0001 is 0.0001 BTC on BTC_USD, passed straight through. The size is rounded down to the pair's step size (0.00001 BTC on BTC_USD).
• A percent is a share of your balance, sized at the current price. q=50% resolved to half of the relevant balance on our test account.

Stops and the trigger price source

A stop is a market or limit order with a trigger attached, and pxs= chooses which price the trigger watches.

e=CRYPTO s=BTC_USD b=sell t=market fpx=95000 pxs=index q=0.0001

pxs=index watches the index price, pxs=last the last traded price, and pxs=mark the mark price, which is the default. The trigger price you set with fpx= (or px=) becomes the order's reference price, and the type resolves to Stop-Loss on a market base or Stop-Limit on a limit base. Crypto.com spot has no attached brackets, so a stop is how you protect a holding: place a sell stop below the market on the balance you want to cover.

Cancelling and exiting on spot

Spot has no position to flatten, so closing works differently here than on a futures broker. You cancel resting orders, and you exit a holding by selling it.

To exit, sell. There is no c=all on Crypto.com spot and c=position does nothing here, because spot has no position record to act on. A market or limit sell for the size you hold is how you flatten.

Cancelling only part of the set

When you have several resting orders, cm= and cmo= let you cancel a subset rather than all of them. cm= is how many (a count or a percent), and cmo= is which ones, by newest, oldest, highest, lowest, biggest, or smallest.

e=CRYPTO s=BTC_USD c=order cm=2 cmo=newest

That cancels the two newest resting orders and leaves the rest working. Without cmo= the engine still honours cm= and takes them in the order it finds them.

What Crypto.com spot does not accept

A few things look like they should work and do not. Knowing them saves a debugging session.

• No c=all and no b=flat. Spot has no position to flatten in one call. Exit by selling the amount you hold.
• c=position does nothing on spot. It reports no position found and changes nothing. It is meaningful only on margin.
• No attached brackets. sl= and tp= in an & section are a futures-broker feature; Crypto.com spot does not read them. Protect a holding with a standalone stop (t=market fpx=) or a limit sell instead.
• No oco= on spot. The one-cancels-other pair is not available on Crypto.com here. Use a single stop or a single limit to manage a holding.
• No trailing stop, iceberg, or leverage. ts=, h=, and the leverage parameters belong to other exchange types.
• One command, one account. You cannot list several accounts with a=acct1,acct2; send a separate command per account.
• u= and y= are ignored here. Crypto.com spot sizes in base units; the unit and yield-basis parameters have no effect.

Everything else on this page resolved to exactly what is described when run through the live Crypto.com zone.

Testing and going live

Append d=1 to any command and Autoview parses it, reports what it would have done, and places nothing:

e=CRYPTO s=BTC_USD b=sell t=market q=0.0001 d=1

That is the safest first run for a command you have just written. Read the log, confirm the pair and side are right and the size is what you meant, then drop d=1 to send it for real. Because Crypto.com orders are real money from the first fill, keep your first live size small and grow it once the alert behaves. For more on reading the log, see test and debug your setup.

Back to the cheat sheet