Rate Limiting

Ensure reliable integrations by managing request volume and preventing system overload.

To maintain platform stability and ensure fair usage across all clients, PCE APIs enforce a rate limiting mechanism. This helps protect the system from excessive traffic while ensuring consistent performance for all integrations.


Rate Limit Policy

Our APIs currently support the following rate limit:

Limit TypeThreshold
Request Limit1000 requests per 10 seconds
ScopePer API client

What Happens When You Exceed the Limit?

If your application exceeds the defined rate limit:

  • The API will return 429: Too Many Requests response
  • Additional requests within the time window will be rejected (dropped)
  • Normal processing resumes automatically once the rate window resets

Best Practices

To ensure a smooth integration experience and avoid throttling:

  • Implement retry logic with exponential backoff
  • Avoid burst traffic by distributing requests evenly
  • Cache responses where applicable to reduce redundant API calls
  • Monitor API usage to stay within thresholds

Recommended Handling Strategy

When receiving 429 response:

  • Pause further requests temporarily
  • Retry the request after a short delay
  • Gradually increase retry intervals if limits continue to be hit

.readme-logo { display: none !important; }