The material presented on this website is for general information purposes only and does not constitute investment advice, or a recommendation or solicitation to exchange, buy, sell, stake, or hold any cryptoasset, or to engage in any specific trading strategy. We do not hold a licence nor are registered in the United Kingdom, and do not actively offer services to UK residents. Please ensure that you fully understand the risks before entering into any transactions. The volatile and unpredictable nature of the crypto-asset markets can result in the loss of funds. Digital assets are complex instruments that involve a high level of risk. This information is not intended for distribution to, or use by, residents of certain countries or jurisdictions, including but not limited to the United States, Iran, Russia, and others, as the Company does not offer its services in these jurisdictions. Geographic restrictions may also apply.

Proactive Monitoring: Check CB-RATELIMIT-REMAINING before making requests. Exponential Backoff: Upon receiving a 429 error, wait before retrying. WebSockets for Real-Time Data: For order book updates, live trades, and tickers, WebSocket connections are significantly more efficient than REST polling. Implement an exponential backoff (e.g., wait 1s, then 2s, 4s, 8s, etc., with jitter) to avoid overwhelming the server. Use WebSocket feeds for real-time data instead of polling REST endpoints. Cache static or infrequently changing data (e.g., product details from /products). Fetch only necessary data.

Trades are virtual. Test balances are typically provided or can be reset.

API Endpoints: Sandbox uses distinct base URLs. A robust deployment strategy includes distinct configurations for Sandbox and Production, primarily differing in API credentials and base URLs. Market Data & Liquidity: Order book depth, trade volume, and price movements are simulated. Order fill simulation might be more simplistic. Trades are virtual. Test balances are typically provided or can be reset. May not perfectly reflect real-world slippage or partial fill scenarios. API Keys: Separate API keys must be generated for. No Real Funds: All assets. Used exclusively with the Sandbox.

Price Priority: Orders with more favorable prices are prioritized (higher price for bids, lower price for asks). API access is subject to rate limits to ensure platform stability and fair usage. Time Priority: Among orders at the same price, the earliest submitted order is prioritized. Understanding this logic is vital for order placement strategies, managing slippage, and fee optimization. Maker: An order that adds liquidity to the order book (e.g., a limit order that doesn’t immediately fill). Taker: An order that removes liquidity (e.g., a market order, or a limit order that fills immediately). Incurs slightly higher fees (e.g., 0.05% – 0.60%). Fee tiers are often based on trailing 30-day volume.