Deriv API

Product updates

USDT and USDC consolidation for payment agents (PAs)

What's new

From 10 November 2026, we're consolidating each payment agent's USDT network balances into one USDT wallet and their USDC network balances into one USDC wallet.

Your existing integrations stay compatible:

  • Endpoint paths don't change.
  • Payment request formats don't change.
  • Legacy PA currency codes keep working during the transition.

We migrate balances and PA currency configurations automatically. While migration runs, we recommend a few minor front-end and mobile changes so your users have a smoother experience. Your other PA currencies, including BTC, ETH, LTC, and USD, aren't affected.

What's changing

Legacy PA currencyNew currencyWhat happens
USDT_TRONUSDTThe code maps to the same underlying balance, so no funds move.
USDT_ETHEREUMUSDTFunds move from the legacy balance into the consolidated USDT balance.
USDC_ETHEREUMUSDCFunds move from the legacy balance into the consolidated USDC balance.

How consolidated configurations are created

If a PA doesn't yet have a USDT or USDC configuration, we create one from their existing legacy configurations:

  • One legacy configuration: We copy the PA's commissions and limits directly.
  • Several legacy configurations, such as USDT_TRON and USDT_ETHEREUM: We copy one complete configuration, chosen by the highest deposit commission. If there's a tie, we use the highest withdrawal commission, then the highest maximum limit, then the lowest minimum limit.

Recommended changes

  • Currency support: Refresh supported currencies, commissions, and limits from GET /payment-agents/v1/agents/{id}, using me for your own agent. Use USDT or USDC for new transfers and withdrawals when they're available for the selected PA.
  • Clients finding an agent: Search with GET /payment-agents/v1/agents?currency=USDT or currency=USDC. When a client changes currency, refresh the agent list and the selected agent's commissions and limits, as consolidated currency terms may differ from legacy terms.
  • Deprecation metadata: Profile currency entries may include the optional field is_deprecated: true. Make sure your integration accepts it. Currencies marked this way still work during the transition.
  • Front-end and mobile displays: Update labels and selectors for USDT and USDC, and avoid showing duplicate USDT choices from the USDT_TRON alias. Hide legacy currencies with a zero balance, and keep those with remaining funds visible.
  • Clients withdrawing via an agent: Check the client's available balance and the selected agent's limits for that currency. Request the OTP, then submit the withdrawal with the same currency, amount, and agent. If any of these values change, request a new OTP.

Transition cases

  • Funds returning to a legacy balance: Existing legacy transactions may settle, or return funds to a legacy balance, after consolidation. Our automatic sweep moves those funds into the matching consolidated currency.
  • Failed withdrawals after an OTP: In rare cases, funds may be swept after a legacy-currency OTP is issued, so the withdrawal fails due to insufficient balance. Once the failure is confirmed, recreate the withdrawal using the consolidated currency and a new OTP. If the original payment is still pending, check its status before retrying.

Legacy currency retirement

Please switch fully to USDT and USDC by 10 December 2026. After this date, USDT_TRON, USDT_ETHEREUM, and USDC_ETHEREUM will stop working as PA-supported currency codes. Until then, existing API calls remain compatible.

For any questions, reach out to your Account Manager or contact us via live chat and WhatsApp.

Payment agents documentation

Markup statistics: a 1-hour data delay and a 6-month query window

What's new

Markup statistics now runs on a new backend. Results exclude the most recent hour of activity, and queries cover only the last 6 months.

Today's figures are still included, but a trade from the last hour won't appear yet. If your date_from is older than 6 months, we'll move it forward to the earliest supported date instead of rejecting the request. Check the date range in the response, and keep your own copy of anything older. Authentication, rate limits, response fields, and status codes are unchanged.

Markup statistics documentation

Documentation: API limits page

What's new

Rate limits for all Deriv APIs are now documented in one place — WebSocket call budgets, REST request caps, and error handling.

No action needed — this is a documentation-only change; API behaviour is unchanged. If your integration retries aggressively or batches calls near a threshold, start with the error-handling guidance.

Read the limits page

New symbols now available on the Deriv API

What's new

New synthetic indices are now available on the Deriv API: Volatility 15 (1s), 30 (1s) and 90 (1s) indices, new Crash/Boom ranges (300–1000), and Range Break 100 and 200.

Each new symbol supports certain trade types only — call active_symbols to see what each one offers. Existing integrations are unaffected; request the new symbols through the same endpoints you already use.

Active Symbols documentation

Buy contracts for multiple accounts in one call

What's new

Buy the same options contract for up to 100 end-user accounts in one REST call.

A 200 response doesn't mean every purchase succeeded — the transactions array carries one entry per account, each either a purchased contract or an error for that account alone. Each account authorises itself, so you don't need your own OAuth token — just the Deriv-App-ID header.

Multiple Buy documentation

Run automated trading strategies over WebSocket

What's new

Seven WebSocket endpoints for running predefined automated trading strategies: you pick a strategy, supply a contract template, and control the run through its run_id.

Pausing and stopping differ in what happens to open contracts. Both halt new purchases: pause holds the run so auto_resume can pick it up later, while stop ends the run and open contracts continue to their own expiry. You can subscribe instead of polling — call auto_get with subscribe: 1 to stream new purchases and status changes until the run ends or you call forget.

Automation API documentation
Click to open live chat support. Get instant help from our support team.