API and Automated Trading Policy

Updated: 9 May 2026

1. Status of this policy

1.1 This API and Automated Trading Policy forms part of the Trading Rules incorporated into the Terms of Use.

1.2 This policy applies to API usage, session keys, bots, algorithms, quote engines, trading systems, automated tools, semi-automated tools, and related activity.

2. User responsibility

2.1 You are responsible for all activity submitted through your wallet, account, subaccount, API keys, session keys, bots, algorithms, trading systems, quote engines, agents, employees, contractors, delegates, service providers, or other automated or semi-automated tools.

2.2 You must implement and maintain appropriate pre-trade and post-trade controls, testing, monitoring, supervision, rate limits, kill switches, error controls, and risk limits to prevent erroneous, excessive, disruptive, manipulative, malformed, unintended, or disorderly orders, RFQs, quotes, cancellations, messages, or transactions.

2.3 You must promptly disable any API key, session key, bot, algorithm, quote engine, or system that is malfunctioning, producing erroneous activity, creating disorderly trading, or otherwise creating risk to users, the Application, the Derive Protocol, market integrity, or orderly operation.

2.4 API users operating automated trading systems, bots, algorithms, or quote engines must maintain written records of pre-deployment testing, system configurations, control settings, and any material changes to those systems for a minimum of 12 months and must make such records available to us on request where reasonably required for a market integrity, Mistrade, Erroneous Transaction, or compliance review.

3. Information requests

We may require users, market makers, liquidity providers, API users, or other participants to provide information about automated trading systems, quote logic, controls, testing, supervision, trading purpose, beneficial ownership, or risk management where we reasonably consider this necessary for market integrity, legal, compliance, security, or operational purposes.

4. Message rates and usage controls

4.1 We may monitor order-to-volume ratios, RFQ-to-trade ratios, quote-to-fill ratios, cancellation rates, message rates, API usage, repeated requests, quote response patterns, latency patterns, malformed messages, error rates, and other activity metrics.

4.2 We may throttle, restrict, reject, review, suspend, or apply additional controls to activity that we reasonably consider excessive, inefficient, disruptive, manipulative, inconsistent with fair and orderly trading, or likely to impose undue burden on the Application, the Derive Protocol, market makers, liquidity providers, users, or related infrastructure, including where message rates, order-to-volume ratios, quote-to-fill ratios, or cancellation rates materially exceed normal operational parameters for the relevant market or instrument.

4.3 We may suspend or revoke API keys, session keys, account access, market access, RFQ access, or other functionality where we reasonably consider this necessary or appropriate.

5. No guarantee

We do not guarantee uninterrupted API availability, latency, execution, message processing, cancellation, quote delivery, order entry, order cancellation, data delivery, or system performance. API unavailability or degraded performance resulting from causes set out in section 14.6 of the Terms of Use does not constitute a breach of these Terms or the Trading Rules. API functionality is provided through the Application layer only and is separate from underlying protocol functionality, which may remain available independently of the Application.

5. No guarantee

We do not guarantee uninterrupted API availability, latency, execution, message processing, cancellation, quote delivery, order entry, order cancellation, data delivery, or system performance. API unavailability or degraded performance resulting from causes set out in section 14.6 of the Terms of Use does not constitute a breach of these Terms or the Trading Rules. API functionality is provided through the Application layer only and is separate from underlying protocol functionality, which may remain available independently of the Application.

6. API data use

6.1 Access to any public or authenticated API endpoint, WebSocket stream, RFQ feed, orderbook feed, market data feed, account feed, or other data feed is subject to the Terms, the Trading Rules, and the Derive Data Usage Policy.

6.2 API access does not create any right to redistribute, commercialise, store, scrape, resell, publish, benchmark, index, or create derived products from Derive Data unless expressly agreed in writing.

6.3 We may restrict, throttle, suspend, terminate, condition, or require separate licensing for API or data-feed access where we reasonably consider this necessary to protect the Application, the Derive Protocol, users, market integrity, infrastructure, data rights, third-party data rights, or commercial data licensing arrangements.

6. API data use

6.1 Access to any public or authenticated API endpoint, WebSocket stream, RFQ feed, orderbook feed, market data feed, account feed, or other data feed is subject to the Terms, the Trading Rules, and the Derive Data Usage Policy.

6.2 API access does not create any right to redistribute, commercialise, store, scrape, resell, publish, benchmark, index, or create derived products from Derive Data unless expressly agreed in writing.

6.3 We may restrict, throttle, suspend, terminate, condition, or require separate licensing for API or data-feed access where we reasonably consider this necessary to protect the Application, the Derive Protocol, users, market integrity, infrastructure, data rights, third-party data rights, or commercial data licensing arrangements.

Trade

About

DRV

Stats

Insights

Enter App