API reference

Rate limits

Each key may send 25 requests a second on average, in bursts of up to 100. The RateLimit headers on each answer show how much of the burst is left, so a client that reads them can slow down before it gets a 429.

The headers

Every answer to a request with a valid key carries three headers.

HeaderWhat it says
RateLimit-LimitHow many requests the key may make in a burst
RateLimit-RemainingHow many of them are left now
RateLimit-ResetSeconds until the burst is full again

Past the limit, Uncart answers 429 rate_limited with a Retry-After header in seconds, and does nothing with the request. Wait that long, then send it again.

The budget belongs to the key, not to the shop. Two systems that share one key also share its budget. Give each system a key of its own.

The size of a request

A request body may be at most 1 MB. A larger one gets 413 body_too_large and is not read.

Pages of a list

A list answers at most limit items, 50 unless you ask for another number from 1 to 200, and a next_cursor. Pass that value as cursor to get the following page. When next_cursor is null there are no more.

A cursor is opaque. Don't build one yourself or keep one for later. Start again without a cursor when you want a fresh list.