Rate Limiting

In order to ensure the stability of the system and to guarantee good performance for all users we have to protect it against deliberate attacks or runaway scripts. Every request which reaches our system will therefore go through a rate limiting filter. As long as the agreed upon rate limiting policies are conformed to, responses by our services shall be delivered in timely fashion. On the other hand, requests which violate any of the agreed upon policies will be responded to with a HTTP 429 response.

We are able to adjust rate limit policies for each individual user so do contact our Support for specific requirements.

Rate limiting policy

A rate limiting policy defines either how many processing units or HTTP requests can be used per given time period or in total. Both processing units and requests are rate limited and the level of rate limiting depends on your account (see pricing plans in billing).

An API is usually protected by multiple rate limiting policies. Epoch's SCo2-API has both a processing unit and request rate limiting policies. To conform to the rate limiter, all rate limiting policies have to be satisfied.

The request rate across all APIs consists of a minute rate limit of 100 requests, and an hourly rate of 1000 requests. For use cases requiring processing more plots than the above-indicated per minute or hour, it is recommended to use the Batch API calls, which allows submitting very large files with thousands of plots.

Unused processing units and requests do not accumulate. If you have a rate limit policy with 100 request per minute and you don't consume any request for a longer period you are still able to do just 100 requests within the next minute.

Rate limiting ramp up

For all SCo2-API subscriptions, the rate limiting is standard as per-above, but for large accounts requiring large volumes of frequent processing, the rate limiting can be configured on a per-client basis.