Each plan has an RPS limit set, and you can find the limits on the Pricing page. Exceeding this limit will result in a 429 Error,429 Client Error: Too Many Requests
You'll be able to view these errors on your Metrics (Endpoints > endpoint-name-example > Metrics)
Remember that batching also counts as RPS because each request is counted individually. Sending a batch with 26 requests while your RPS is 25 will result in 25 valid responses and one (1) error. The JSON structure will still be valid, but you might run into parsing errors in your code if you only expect valid responses and not 429 errors.
Preventing the error
You can deal with these 429 errors in many different ways:
Add a delay or timeout before a retry. Retry your request using increasing pauses in between
Calculate beforehand how many RPS you'll be doing
Use a third-party package to throttle based on a fixed number, such as
Each plan has an RPS limit set, and you can find the limits on the Pricing page. Exceeding this limit will result in a 429 Error,
429 Client Error: Too Many RequestsYou'll be able to view these errors on your Metrics (Endpoints > endpoint-name-example > Metrics)
Remember that batching also counts as RPS because each request is counted individually. Sending a batch with 26 requests while your RPS is 25 will result in 25 valid responses and one (1) error. The JSON structure will still be valid, but you might run into parsing errors in your code if you only expect valid responses and not 429 errors.
Preventing the error
You can deal with these 429 errors in many different ways: