Vorgio

Rate limits

Every API token has its own rate limit, expressed in requests per minute, applied per token (not per IP, not per team). The platform default for a fresh token is 60/min.

#Configuring the limit

A team owner or admin sets the limit in the API tokens UI under team settings. The form has a numeric input "Rate limit (requests per minute)" with these rules:

  • Floor: 30 req/min. The form refuses anything below 30. The server clamps any below-30 value to 30 at request time, so a stale or hand-edited row can't bypass the floor.
  • No upper cap in the UI — owners and admins can dial as high as they need. If you need more than a few hundred per minute, talk to Vorgio support first; sustained burst capacity may need infrastructure tuning.

The list of issued tokens shows each token's per-minute limit alongside its name and last-used timestamp.

#Why the floor exists

A misconfigured low limit silently breaks a team's own integration. If your shop has even a modest checkout burst (a flash sale, a marketing email going out at 09:00), a 1/min token will start 429-ing within seconds. The 30/min floor is one request every two seconds — comfortably above any sane checkout rate, and low enough not to waste platform headroom on under-utilised tokens.

#The 429 response

When you exceed the limit Vorgio returns 429 Too Many Requests with the standard RFC 7807 envelope:

 1HTTP/1.1 429 Too Many Requests
 2Retry-After: 17
 3Content-Type: application/problem+json
 4
 5{
 6  "type": "https://vorgio.app/problems/too-many-requests",
 7  "title": "Too Many Requests",
 8  "status": 429,
 9  "detail": "Rate limit exceeded. Try again in 17 seconds."
10}

The Retry-After header tells you how many seconds until your next request will be allowed. Always honour it — retrying sooner just deepens the throttling window.

#Recommended client-side back-off

For the synchronous POST /v1/checkouts path (where a customer is waiting on a checkout button):

 1function vorgioCallWithRetry(callable $do, int $maxAttempts = 3) {
 2    for ($i = 0; $i < $maxAttempts; $i++) {
 3        try {
 4            return $do();
 5        } catch (RateLimitedException $e) {
 6            if ($i === $maxAttempts - 1) throw $e;
 7            sleep(min($e->retryAfter, 5));   // cap to 5s — customer is waiting
 8        }
 9    }
10}

For batch / async paths (e.g. nightly import of a backlog of orders) you can sleep the full Retry-After and resume.

#Per-token, not per-team

Each token has its own bucket. If you issue separate tokens for separate environments (recommended) or for separate workloads (e.g. one for checkouts, one for cron-driven mark-paid sync), they don't compete.

 1Vorgio team
 2├── token "wp-prod"    — 120/min, used by checkout flow
 3├── token "wp-cron"    — 30/min, used by nightly mark-paid sync
 4└── token "wp-staging" — 30/min, on a totally separate WP install

The checkout-flow token can exhaust its bucket without blocking the nightly cron, and vice versa.

#What about webhooks Vorgio sends to you?

Webhooks aren't rate-limited from your side — Vorgio simply respects whatever your endpoint can handle, with the documented retry schedule (see Webhooks). If your endpoint can't keep up, return 2xx quickly and process asynchronously. Don't try to "throttle Vorgio" by responding slowly — slow responses count as failures and trigger retries.