API Reference
Log inSign up
v.1.7.2
v.1.7.2
  • Introduction
  • Integration
  • Sandbox and Live
  • Authentication
  • Rate Limits
  • Service Quota
  • Errors
  • Pagination
  • Filtering
  • Versioning
  • Core resources
  • Clients
    • Create a client
    • Get a client
    • Update a client
    • Delete a client
    • List clients
    • Filtering clients
  • Addresses
    • Create an address
    • Get an address
    • Update an address
    • Delete an address
    • List addresses
    • Filtering addresses
  • Documents
    • Create a document
    • Get a document
    • Update a document
    • Upload image attachment
    • Download image attachment
    • Delete image attachment
    • Delete a document
    • List documents
    • Filtering documents
  • Live Photos
    • Upload a live photo
    • Get a live photo
    • Download live photo
    • Delete a live photo
    • List live photos
  • Checks
    • Create a check
    • Get a check
    • Update a check
    • Validate check outcome
    • List checks
    • Filtering checks
  • Risk Profile
    • Get a risk profile
  • Check types
    • AML Screening Check
    • Document Check
    • Identity Check
  • Other Resources
    • Webhooks
      • Create a webhook
      • Get a webhook
      • Update a webhook
      • Delete a webhook
      • List webhooks
      • Filtering webhooks
    • Reports
      • Generate a client report
      • Generate a check report
    • SDK Tokens
      • Generate a token
    • Team Members
      • Get a team member
      • List team members
      • Filtering team members
    • Audit Logs
      • Get an audit log
      • List audit logs
      • Filtering audit logs
Powered by GitBook
On this page

Was this helpful?

Rate Limits

Understand how ComplyCube rate limiting works.

ComplyCube’s API enforces a maximum rate limit of 100 requests per minute. For Sandbox requests, the rate limit is 30 requests per minute.

These are hard limits that may not be increased. Any request over the limit will return a 429 Too Many Requests error.

You must implement suitable error handling for429errors. Using an exponential backoff with a random jitter is the recommended way to handle such errors.

Avoiding the limit

The tips below are some simple suggestions to help reduce the possibility of being rate limited. We recommend:

  • Running non-essential or routine batch API jobs outside your peak hours.

  • Throttling or avoiding batch jobs.

  • Implementing exponential back-off retries, with an initial delay of 30 seconds.

  • Prioritising requests that are essential to verify an active user.

  • Use our webhooks instead of polling our API.

PreviousAuthenticationNextService Quota

Last updated 4 years ago

Was this helpful?