Developing a Trading Bot with REST API Control

When developing trading bots for DeFi, we face a critical problem—duplicate orders due to network timeouts. Without idempotence, the same signal can lead to double execution and losses. For example, during a sharp price move, a sell signal may not reach the exchange, and the bot resends it—without idempotence, this results in an excess position. REST API with an Idempotency-Key is the standard solution used by all major exchanges. Our team has 10+ years of experience in trading system development, with over 50 completed projects. The retry error occurs in 2–5% of cases during high volatility; idempotence eliminates it entirely.

"Idempotence is the property of an operation that allows it to be performed multiple times without changing the result." — Wikipedia

How REST API Solves the Duplicate Order Problem

Each trading request contains an Idempotency-Key header—a unique UUID. The client generates a key for each new command; the server stores the result for 24 hours. If a duplicate request with the same key arrives within that time, the cached response is returned—the trade is not duplicated. This is especially important when working with high volatility and frequent RPC interruptions. We also implement a retry mechanism with exponential backoff to guarantee delivery.

Why Asynchronous Model is Better for Trading

Synchronous execution blocks the client until the exchange responds (100–500 ms). Asynchronous approach: the API returns 202 Accepted with a job ID, and the result is fetched separately via GET /jobs/{id}. This approach allows processing up to 10,000 requests per minute per bot instance. HMAC-SHA256 signing takes less than 1 ms, and total latency does not exceed 10 ms. This reduces commission costs by 15–20% due to more precise order execution.

How We Build a Fault-Tolerant System

We implement a circuit breaker to protect against overloads. If the error rate exceeds a threshold, the API temporarily rejects requests, allowing the backend to recover. Monitoring via Prometheus and alerts for 429, latency, and drop rate. History of responses with idempotency key is stored in Redis with a 24-hour TTL.

Management Endpoints

Full list of endpoints is in the OpenAPI 3.0 documentation.

Rate Limiting and Timeout Handling

Rate limiting protects against accidental spikes and abuse. Example response headers:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 87
X-RateLimit-Reset: 1704067260

Limits are differentiated: status reads — 300 req/min, trading operations — 30 req/min. On exceeding — 429 Too Many Requests with a Retry-After header. We configure these limits according to your strategy and volumes. Downtime reduction reaches 99.9%.

Authentication: API Keys + HMAC

The standard for trading APIs is request signing with HMAC-SHA256. The key is never transmitted in the request, only the signature. IP whitelisting and scoped keys:

Webhooks for Events

We use a push model for event notifications. Register an endpoint with a URL and event types (trade.opened, position.closed, bot.error). When the event occurs, the bot makes a POST with the payload.

Reliable delivery: exponential backoff, signature verification, log of all attempts. Integration with external systems or orchestration of multiple bots is a standard scenario. Get a consultation on configuring webhook integration.

Work Process

1. Analytics — studying strategies, volumes, infrastructure.
2. Design — agreeing on endpoint schema and security model.
3. Implementation — writing code in TypeScript/Go with viem and ethers.js.
4. Testing — unit and integration tests with an exchange simulator, load testing up to 10,000 req/min.
5. Deployment — CI/CD, monitoring (alerts for 429, latency).

Timelines: from 2 to 4 weeks depending on complexity. We will evaluate the project after a brief—contact us for a consultation.

What's Included

• REST API with OpenAPI 3.0 documentation
• Source code in a private repository
• Integration with exchanges of your choice
• Webhook endpoint for events
• Load testing (up to N requests/min)
• Deployment instructions
• 1 month of support after release

Order the development of a custom API—let's discuss the task.

Why exchange development requires deep domain expertise

We develop exchanges — not 'chart sites,' but matching engines that process thousands of orders per second without delay, route liquidity between pools, and guarantee that no user gains access to others' funds. Teams that start with the UI and postpone the engine 'for later' end up rewriting everything in six months in 90% of cases.

Order Book vs AMM: where most projects break

Centralized exchanges (CEX) are built around an order book + matching engine. Decentralized exchanges (DEX) either also use an order book (dYdX on StarkEx, Serum/OpenBook on Solana) or an AMM with concentrated liquidity (Uniswap v3/v4, Curve, Balancer). A classic mistake when developing a CEX is implementing the matching engine on top of a relational database with transactions for each match. PostgreSQL handles ~500 RPS without special effort, but at peak loads of 5,000–10,000 orders per second, it turns into a deadlock nightmare. The correct architecture: in-memory order book (Redis Sorted Sets or custom C++/Rust structure), asynchronous writing of matches to PostgreSQL via a queue (Kafka/RabbitMQ), and a separate settlement service that finally updates balances.

For DEX, the most painful problem is sandwich attacks and MEV. A pool with a plain xy=k AMM without slippage protection becomes a target for MEV bots within hours of launch. Uniswap v2 lost hundreds of millions of dollars in user liquidity. Solutions: integration with Flashbots Protect, a commit-reveal scheme for orders, or switching to TWAMM (Time-Weighted AMM) for large trades.

Concentrated liquidity and impermanent loss

Uniswap v3 introduced concentrated liquidity – LPs choose a price range in which to provide liquidity. Capital efficiency increased 4,000x compared to v2 for stable pairs. But implementing this mechanism correctly is non-trivial. The Uniswap v3 liquidity contract uses tick-based accounting: the price space is divided into discrete ticks (tick = log₁.0001(price)), each tick stores accumulated fee growth and liquidity delta. When creating a position, the lower and upper ticks are computed, and the contract recalculates all active positions at each swap. Storage layout is critical here – incorrect variable packing in slots easily adds 40–60% to swap gas cost.

We implemented a Uniswap v3 fork for a client on Polygon with a custom fee tier system. The initial version consumed 180k gas for a swap across 2 ticks. After slot packing of variables in Tick.Info and inlining several internal calls, it dropped to 112k gas. This reduced gas costs by 38% and saved the client substantial costs on fees monthly. The techniques applied are described in the Uniswap v3 Whitepaper and confirmed by our audit experience.

How a matching engine delivers performance

A production-ready matching engine is built according to the following scheme:

• Order ingestion layer – WebSocket gateway (Go or Rust), accepts orders, validates signature, checks balance via Redis, queues them. Latency at this level must be <1ms.
• Matching core – single-threaded event loop (eliminates race conditions without mutexes). In memory, we hold two Sorted Sets for each trading instrument: bids and asks. FIFO matching for limit orders, immediate-or-cancel for market orders. Throughput with a proper Rust implementation – 500k–1M matches per second on a single core.
• Settlement service – reads matches from Kafka, atomically updates balances in PostgreSQL (UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1). Optimistic locking via row versioning.
• Withdrawal pipeline – separate service with cold/hot wallet architecture. The hot wallet holds 5–10% of total deposits, the rest is cold storage with multi-sig (Gnosis Safe or custom HSM). Automatic withdrawals only from hot wallet, large amounts require manual authorization.

How our exchange development process ensures reliability

Smart contracts and gas optimization

For EVM-based DEX (Ethereum, Arbitrum, Optimism, Polygon), the entire critical path lives in Solidity. Main contracts: Pool, Factory, Router, PositionManager (for v3-like), and Quoter for off-chain calculations. Typical mistakes we see in audits:

Reentrancy via callback. Uniswap v3 uses flash swap with a callback (uniswapV3SwapCallback). If your router lacks a nonReentrant guard and you don't check msg.sender == pool, the contract gets drained via a nested call. This is not hypothetical – several v3 forks lost funds this way.

Oracle manipulation in AMM. If your contract uses the spot price from the pool for collateral calculation, it is front-runnable. Correct: TWAP over 30+ minutes (Uniswap v3 OracleLib) or an external oracle (Chainlink).

Unbounded loops in liquidity range. If a swap crosses many ticks in a row (price impact 80%+), gas may exceed the block limit. Need MAX_TICKS_CROSSED with partial fill and returning the remainder.

For Solana DEX (Anchor framework, Rust), the architecture is fundamentally different: account-based model, Program Derived Addresses (PDA) instead of storage, Cross-Program Invocations instead of internal calls. Solana's throughput (~3,000–4,000 TPS vs 15–30 on Ethereum mainnet) allows building on-chain order books – exactly what Phoenix DEX does.

Liquidity bootstrapping and aggregator integration

Launching a pool is not enough – you need to ensure liquidity at launch. Practical mechanisms:

• Liquidity Bootstrapping Pool (LBP) – initial price is high, asset weights dynamically shift, creating selling pressure and even token distribution. Implemented in Balancer v2.
• Initial Liquidity Offering via Uniswap v3 – adding liquidity in a narrow range around the initial price, then gradually expanding as volume grows. Requires active liquidity management or integration with Arrakis/Gamma.
• Integration with 1inch, Paraswap, Li.Fi – aggregators bring traffic but require standard compliance: the pool must have correct getAmountsOut, support ERC-20 approval/permit, and not have custom transfer hooks that break the aggregator's routing.

Development process and deliverables

Analytics and design begin with choosing the architectural model: CEX with custodial storage, non-custodial DEX, or hybrid (off-chain order book + on-chain settlement, like dYdX v3). This decision determines everything – regulatory load, tech stack, team.

Development proceeds in layers: first smart contracts with full Foundry coverage (fuzzing, invariant testing), then backend services, then integration layer, and finally frontend. Testing includes fork testing on mainnet via Foundry – we reproduce real liquidity conditions, not synthetic ones.

Audit is mandatory before mainnet deployment. For DEX contracts, minimally one firm with manual review (Trail of Bits, Spearbit, Code4rena contest). For CEX custody, audit of key storage processes. We guarantee all contracts undergo formal verification and fuzzing testing (Echidna, Foundry invariant).

Estimated timelines

Cost is calculated individually after a technical briefing: chain selection, throughput requirements, custodial model. Our certified engineers with 10+ years of experience will help you choose the optimal architecture and avoid common pitfalls. Contact our team for a detailed proposal.

Pitfalls to avoid at launch

• Forgetting the price oracle in AMM. Spot price can be manipulated with a flash loan in one transaction. If your lending protocol uses the spot price from its own pool, that's a bug.
• Hot wallet without limits. A CEX without daily limits on automatic withdrawals is an invitation for attackers. Compromising one key should lose at most 10% of total funds.
• Absence of circuit breaker. A 40% price drop in 5 minutes should halt automatic liquidations or withdrawals until manual review. Without this, a cascading liquidation spiral destroys all TVL.
• Incorrect decimal handling. USDC uses 6 decimals, WBTC – 8, most tokens – 18. Mixing without normalization leads to either precision loss or overflow. Solidity has no float; we work with fixed-point using FullMath (mulDiv with overflow protection).

Want to avoid these problems? Get a consultation — we will select the architecture for your project and provide exact timelines. Order exchange development with quality guarantee and ongoing support.