Rate Limits

Sandbox Limits

In order to protect Sandbox stability DriveWealth imposes a rate limit of 5 requests per second. The limit is set per dw-client-app-key.

It's common for partners to prepare for production style events by load testing their systems, with the DriveWealth API running in Sandbox as part of it. We generally discourage this practice because API limits are lower in Sandbox, so the load test is likely to hit limits that it wouldn't hit in production. Sandbox is also not a perfect stand-in for live API calls, and that can be subtly misleading. For example, creating an order in production sends a request to an order gateway and execution venue, while that request will be mocked in test mode, resulting in significantly different latency profiles.

Production Limits

As of today, DriveWealth imposes rate limits on specific endpoints that are high latency | low throughput, or those that otherwise don't rationally make sense to be called numerous times per second. The below table defines these limits:

MethodEndpointLimit (requests / second)
GET/users/id/documents5
GET/countries5
POST/auth2
GET/documents/id/url5
POST/accounts/transfer100
GET/accounts/{accountID}/violations5
GET/accounts/search5
GET/users/{userID}/accounts5
GET/users/{userID}100
PATCH/users/{userID}100
GET/users/{userID}/kyc-status10
GET/instruments/{instrumentID}15