OANDA · Rate Limits
Oanda Rate Limits
OANDA v20 REST API rate limits apply per authenticated user. New streaming connections are throttled to 2 per second; persistent HTTP connections support up to 100 requests per second. Aggregate streaming connections are capped at 20 across all sessions.
Oanda Rate Limits is the machine-readable rate-limit profile for OANDA on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 6 rate-limit definitions, measuring requests, connections_per_second, requests_per_second, connections, and records.
The profile also includes 4 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Rate Limiting, Forex, and Trading.
6 Limits
Throttle: 429
Rate LimitingForexTrading
Limits
Per-user request limit user
30
New connection rate global
2
Persistent connection throughput connection
100
Aggregate streaming connections account
20
Historical candle records per page request
5000
FIX API default message rate session
100
Policies
Persistent connections preferred
Use HTTP persistent (keep-alive) connections to reduce per-request latency and avoid triggering the new connection rate throttle.
Account state sync pattern
Initialise with a full account snapshot via GET /v3/accounts/{accountID}, then poll GET /v3/accounts/{accountID}/changes with the last TransactionID to receive only incremental updates.
Streaming connection management
Open streaming connections sparingly; reconnect with exponential backoff on disconnect. Do not exceed 20 aggregate streaming connections per account.
Backoff on errors
Implement exponential backoff when receiving rate limit or server error responses to avoid sustained throttling.