The Daisycon API uses a throttling mechanism to limit the amount of calls an API-user can make. This mechanism reduces the strain on our backend systems, as well as prevents multiple users to compete for resources. This will result in less downtime and error responses.
Currently our API has been limited at 2.500 requests every hour per IP address. (The sandbox environment has a lower rate limit, please check out our sandbox page).
NOTE: Starting November 16th, 2020, the rate limit will change to 25 API calls API per minute per IP address.
When the amount of requests exceeds your limit, the API lets you know by giving a HTTP response code 429 (“Too many requests”). If you get this error, please reduce your request rate. If this occurs, you’ll have to wait until you regain your requests the next minute. Fortunately, this should not occur, or rarely occur. If this does occur regularly, please contact your API administrator to discuss your throttling profile.
Make sure your code doesn’t make calls twice and try to improve your code to reduce the amount of API calls made.
Using webhooks can also greatly reduce the amount of API calls made. Webhooks will be fired when an event occurs. You can, for example, set up a webhook that will call a URL on your side of the application when a new order has been created or a payment has been made.
The Daisycon platform uses multiple database machines. In most cases, these machines contain (exactly) the same data. However, developers have to keep in mind that sometimes, when the data has to be replicated to multiple machines, there can be latency. The latency is usually just a few seconds, but can sometimes be minutes too.