> For the complete documentation index, see [llms.txt](https://apidocs.gsped.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.gsped.com/gsped-api-english-version/overview/throttling.md).

# Throttling

Limits on consecutive calls

To maintain a high level of service, GSPED applies throttling rules to API calls.

The table below shows the limits that must not be exceeded.

{% hint style="info" %}
**The limits refer to 5-minute intervals**
{% endhint %}

| Call type               | Call limit |
| ----------------------- | :--------: |
| All POST calls combined |     450    |
| Shipment POST           |     300    |
| Shipment Confirm POST   |     300    |
| DELETE calls            |     600    |
| GET calls               |    1200    |

Exceeding these limits returns 403 - FORBIDDEN

{% hint style="warning" %}
The same **403** code is also returned when the API key is not valid: in that case the response body is `{"status": false, "error": "Invalid API key "}`.

If the API key is correct and you still receive a 403, check that you have not exceeded the limits above and wait for the end of the 5-minute interval before repeating the call.
{% endhint %}

For calls to the tracking endpoint, we suggest not calling more than once per hour for a single shipment, considering that on average Gsped systems query the courier systems every 60 minutes.

Also regarding tracking, you can request the activation of webhooks to your own systems, avoiding polling Gsped.