Rate Limits

In order to maintain an adequat level of services for all API users and to defend itself against denial-of-service attacks, givve has introduced limits for how frequent you may issue requests.

How do I notice that rate limiting kicked in?

The HTTP response to any API request will have status code 429 TOO MANY REQUESTS and the body will say the same (in the Content-Type desired).

How long will my requests be blocked?

In the HTTP response header of every request to our API you will find

Additionally, when rate limiting already kicked in, you will also see

From this you can infer

X-RateLimit-Limit: The maximum number of requests which can be issued to this endpoint within a certain time span.

X-RateLimit-Remaining: The number of requests which you can still issue until rate limiting kicks in.

X-RateLimit-Reset: The UNIX timestamp at which X-RateLimit-Remaining will be reset.

Retry-After: The number of seconds you will have to wait until you can issue requests again to the given endpoint.

How high are the rate limits?

Take "300 requests within a window of 5 minutes" as a rule of thumb. The resource and rate limits, and the default and maximum sizes of paged data are not considered part of the API. givve reserves the right to adjust them (possibly dynamically) if the operational situation makes it necessary to uphold the service.

How can I get higher rate limits?

We're afraid you cannot. The rate limits apply to all API users equally and are carefully tailored to offer you the best experience possible while still being able to uphold the service.

How do I notice that rate limiting kicked in?#

How long will my requests be blocked?#

How high are the rate limits?#

How can I get higher rate limits?#

How do I notice that rate limiting kicked in?

How long will my requests be blocked?

How high are the rate limits?

How can I get higher rate limits?