Relyence API Rate Limiting

To help maintain consistent and reliable application and API performance, Relyence applies rate limiting to API requests. Relyence evaluates API activity over a rolling 60-second window. Different request types may count differently toward the limit based on the resources required to process them. Specific usage thresholds may be adjusted as Relyence tunes service performance, so integrations should not depend on a fixed number of requests per minute.

In addition, only one API request per organization can be in progress at a time.

If an API request is throttled, Relyence returns an HTTP 429 (Too Many Requests) response. The response may include a Retry-After header indicating the number of seconds to wait before retrying the request.

 API integrations should be designed to:

• Detect HTTP 429 responses.
• Wait for the amount of time specified in the Retry-After header, when it is provided, before retrying the request.
• Use exponential backoff when the Retry-After header is not provided.
• Avoid sending multiple Relyence API requests concurrently.

 For an example of how to implement retry handling in C#, see the Relyence API Retry Example. You can copy the applicable code into a C# source file and adapt it to your integration.