Availability, scaleability and security and so much more reasons to rate limit the access to the wunderbon network - But why? With starting the 1st public release we attracted not only customers but also a bunch of curious people, no matter of intention. So we were faced with a situation where we want to ensure high availability, speed and security/trust and on the other side control having to control the traffic which is not intended for good. For this reason we are - as many other APIs out there - working with a fair use API rate limiting which just separates between unauthenticated and authenticated users.
To ensure availability, stability and fair use wunderbon controls the frequency with which the wunderbon API can be accessed. However, the procedure known as
Rate Limiting is designed so generously that all concerns are taken into account.
Authenticated & Unauthenticated
Regardless of whether you are authenticated or not, wunderbon limits the frequency at which the wunderbon API can be accessed. Thus ensures high availability and a fair distribution of resources.
You can make up to 5.000 API requests per hour. Authenticated requests are associated with the authenticated user, regardless of Authentication-Type or -Scheme used. This means that all applications authorized by a user share the same quota of 5.000 requests per hour. This will apply also when they are authenticated with different tokens owned by the same user.
For unauthenticated requests, the rate limit allows for up to 60 requests per hour. Unauthenticated requests are associated with the originating IP address, and not the user making requests.
/tokens/authentication will allow not more than 30 requests within a window of 60 minutes. There is no reset.
The returned HTTP headers of any API request show your current rate limit status:
curl -Li https://playground-api.wunderbon.io/users/69811200-926b-40ca-8ad4-707f6ecbd0b7
HTTP/1.1 200 OK Date: Mon, 01 Jul 2020 17:27:06 GMT Status: 200 OK x-ratelimit-limit: 5000 x-ratelimit-remaining: 4523 x-ratelimit-reset: 1372700873
Updated almost 2 years ago
Continue with our guided tour. Now, we would like to tell you more about
Resultsets and how we return data from the wunderbon API ...