BitGo · Rate Limits

Bitgo Rate Limits

The BitGo Platform API applies per-access-token request rate limits. When a client exceeds the allowance the API returns HTTP 429 (Too Many Requests). BitGo does not publish a single fixed public number for all accounts; limits are enforced per token and can be raised for enterprise customers under a commercial agreement. Specific per-endpoint values are not reconciled in this artifact.

Bitgo Rate Limits is the machine-readable rate-limit profile for BitGo on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Digital Assets, Custody, Wallets, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Digital AssetsCustodyWalletsRate LimitingQuotasThrottling

Limits

Requests Per Token token
requests
see provider documentation
Per-access-token request throttling; exceeding it returns HTTP 429.
Enterprise Elevated Limits enterprise
requests
negotiated
Higher throughput available to enterprise customers by agreement.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Express Proxy
Run BitGo Express for local signing; it proxies to the platform and is still subject to platform rate limits.

Sources