VeePee API Limits and Pagination
Summary of Changes: (The purpose of this table is to keep traceability and Product team to highlight the things that were changed into the scope, based on comments or discussions)
| Version | Date | Created / Updated | Notes |
|---|---|---|---|
| 1.0 | 25.01.23 | Bogomil Pavlov | First publish |
| 1.1 | 06.03.23 | Bogomil Pavlov | Add the limit per file |
Pagination
You can control the pagination using the parameters limit and offset.
We paginate the results with the offset and limit get params. By default limit is 50. You can increase up to 100.
File Size Limit
Each feed we are generating must be at most 80mb, otherwise we will receive an error.
Rate Limit
As a security measure, every token has limited the number of calls they can make on the API. On every call, you will find how many calls you have available and how many you have consumed. You will find this information on the headers of the response:
X-Rate-Limit-Limit →100 (Number of available calls)
X-Rate-Limit-Remaining →96 (Number of calls remaining)
X-Rate-Limit-Reset →18 (Number of seconds to wait before having the maximum number of allowed requests)
The amount of available calls you can make is refreshed every 10 minutes. If you exceed your number of petitions, you will receive a Too Many Requests Exception (HTTP code 429). If you consider that the number to be too low for your needs, contact our API Manager to increase the limit.
The best case for us is to wait until we limits are refreshed however if for some reason we hit the limits the relevant errors messages should be stored . Also please note if we are getting a lot of orders and getting them page by page if we hit a limit we have to make sure we wont break something and store orders with missing information.
Please note the limit is per API key not account so if we have couple of accounts in Hemi with the same API key we need to share the limit!