GorillaDesk · Rate Limits

Gorilladesk Rate Limits

The GorillaDesk v1 API enforces per-endpoint-group rate limits to protect its infrastructure. Endpoint groups bundle URL paths and HTTP methods together (for example, GETs to /v1/users and POSTs/PUTs to /v1/customers may count as two different groups), letting GorillaDesk allow a higher limit on lightweight requests than on heavier ones. The API does not publish fixed numeric limits; it states the limits are high enough that typical workflows are unaffected. Clients learn their live limit from response headers and must back off on 429.

Gorilladesk Rate Limits is the machine-readable rate-limit profile for GorillaDesk on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Field Service Management, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Field Service ManagementRate LimitingQuotas

Limits

Endpoint Group Requests company
requests
not published
Limits are enforced per endpoint group (path + method) and are not published as fixed numbers; read x-rate-limit-* headers.
Lightweight Requests company
requests
higher (unspecified)
GET-style lightweight requests are grouped to allow a higher limit than resource-intensive requests.

Policies

Honor Rate Reset on 429
On a 429 (Too Many Requests) response, sleep/pause for the number of seconds indicated by the rate_reset / x-rate-limit-reset value before retrying that endpoint.
Per-Endpoint-Group Enforcement
Rate limits apply per endpoint group rather than globally, so throttling on one group does not necessarily throttle another.
Backoff Strategy
Implement exponential backoff with jitter and monitor x-rate-limit-remaining to avoid hitting the limit.

Sources