Add-on API limitations

Automatic control

All verified add-ons are monitored by our automatic control. This automatic control checks the API you use against what you have set in the Marketplace (the development part of the add-on).

If such an add-on subsequently deviates from this predefined format, the control will notify us and we will contact you to jointly identify the cause and ensure a remedy.

If the Agency does not respond to the call for correction, the automatic control will suspend the add-on on all projects that have it activated.

API limits

Verified add-ons are not limited by the number of requests by default. For now, we rely on the fact that through the approved verified add-on we have concluded a certain "unwritten" form of cooperation, that you will try to use the Upgates API in the most optimized form possible, and that you will not switch to "chaos mode" immediately after approval of the add-on. In return, you will get some freedom in the number of requests per day compared to a regular API user and the API will not be charged.

Unlike this regular API user, the check after a certain number of requests (see below) will not stop you, but will only alert us to an add-on that does not behave normally, either within the number of requests or deviates from what you defined in the Marketplace.

The automatic check is currently set to monitor the maximum number of requests as if it were the largest tariff with all API expansion packages. That is, 60,000 per day (see limitations here).

However, there is no need to reach this limit at all, so you have technical consultation available during development and you can always consult with us on how to best use the API. Most add-ons will subsequently reach a maximum of a few thousand per day. The more optimized the add-on you make, the less expensive the subsequent administration will be for both parties.

Be careful! However, the goal should not be to pass on the fact that it makes a maximum of 59,000 requests per day and that is fine. It is still necessary to ensure that the API utilization is as low as possible.

Why are there limits?

It is important for both of us to remember that the Client does not only use your add-on. Although this may be the case at the beginning, over time they can activate any number of add-ons. If each such add-on did whatever they saw fit, the server would become very busy very quickly and our operating costs would increase unbearably.

Please note that during technical calls / approval and testing process (online / ticket) we do not try to make the approval process of your add-on difficult, but we try to prevent future problems.

Example:
A project has 10,000 products whose availability is updated via supplier feed every 2 hours, 5 languages ​​and 4 connected add-ons. Each of the add-ons works with the products in a certain way.

Every 2 hours (updating the supplier feed on availability), Upgates will trigger a webhook on Products.update

• If the add-ons did not use pagination: 480,000 requests per day (10,000x(24h/2h)x4add-ons)
• If the add-ons downloaded languages ​​separately: 2,400,000 requests per day (10,000x(24h/2h)x5languagesx4add-ons)
  
  
• In contrast, the optimized solution: 9,600 requests per day (10,000/50x(24h/2h)x4add-ons)*
  *The add-ons used pagination (50 products per page), and they also download products in a general form without dividing them into mutations (they divide the mutations up to themselves).

This number of products, languages, and add-ons is quite common on Upgates, in fact the vast majority are clients with multiple products and dozens of languages.