Rate Limits

Rate limits exist to protect against bursts of activity and maintain stability. If you send too many requests in quick succession, a 429 error response code might be returned.

Additional rate limit restrictions apply to wallet creation requests and disbursement creation requests, depending on the worker identification method your organization provides.

Common rate limit error causes

• Large volume of closely-spaced requests
• Many long-lived requests

Handling

• Watch for 429 error response codes and build a retry mechanism.
• Use exponential backoff.
• Use a token bucket to globally limit requests to the available tokens in the bucket. If substantial rate limiting is detected, decrease the bucket's token capacity or decrease the token refresh rate.

Endpoints with additional rate limit restrictions

• Create Wallet: 1 request / second
• Create Disbursement: 5 requests / second