API Rate Limits

Omisell throttles authenticated requests to api.omisell.com. Requests to other hosts are not counted.

General API rate limits

The limit is a fixed 60-second window, counted per seller account — the counter key is user + country + business. It is not per shop and not per API key: every shop and every key of the same account share one counter.

Limit:  100 requests
Window: 60 seconds

The first request opens the window; each following request increments the counter. Once the counter reaches the limit, every further request is rejected with HTTP 429 until the window expires, at which point the counter resets to zero in one step.

WARNING

The counter does not drain gradually. Spending all 100 requests in one second is allowed, and the account then waits for the rest of the window. Pacing your app at a steady rate does not raise the ceiling — it only avoids hitting it early.

Rate limits header

Responses in the throttled scope carry the current usage:

X-Omisell-Api-Call-Limit: 32/100

32 is the number of requests already counted in the current window, 100 is the limit.

429 response

{
    "data": {
        "retry_after": 47,
        "rate_limit_on_time": 60,
        "rate_limit_remaining": 0,
        "rate_limit": 100
    },
    "error": true,
    "error_code": 429,
    "attr_error": null,
    "messages": "Request was throttled. Rate limiting 100/100. Expected available in 47 seconds."
}

Retry after data.retry_after seconds — that is the exact number of seconds left in the current window.

General API rate limits#

Rate limits header#

429 response#

General API rate limits

Rate limits header

429 response