How to call our APIs
Rate Limits
Initial API limits
We start each client with conservative API limits designed to avoid accidental misuse.
| Operation | Per second per customer | Per second per shop | Per day per customer | Per day per shop |
|---|---|---|---|---|
| Reads | 2 | 100 | 1 000 | 500 000 |
| Blocks displayed | 3 | 200 | 1 000 | 500 000 |
| Writes | 2 | 100 | 200 | 100 000 |
Important consequence of these limits
Note the low per customer per second read limits. We want you to fetch all the data you need to display a given customer page in one or two API calls. Please don't e.g. make separate duplicate fetch requests in each React component of your app.
This is only designed to prevent accidental misuse. If you have a legitimate need to make more calls per customer, we'll be happy to accomodate.
Increasing the limits
As you approach production, please tell our development team if you need an increase.
Our platform will comfortably sustain at least the following load:
| Operation | Per second per shop |
|---|---|
| Reads | 20 000 |
| Blocks displayed | 20 000 |
| Writes | 1 000 |
Hitting API limits
Our platform will start delaying your requests as you hit these limits. We'll refuse to delay by more than 5 seconds, though, in which case we'll be returning HTTP 429 Too Many Requests error responses. We'll send a Retry-After header to tell you when it's safe to retry the calls.