API reference
Read your request bounds
The concurrency, patience, rate and burst your requests are held to, from the table the door enforces.
GET
The four numbers your requests are held to, read from the same table the door enforces them from. What this answers is what the door applies.
A request within these numbers is never refused for a bound. The bounds are counted per process, so where the Platform runs more than one you may be admitted more. That excess is never promised: a refusal beyond the numbers is answered as any bound refusal.
Size your parallelism from them. Reads take no lock and may be sent in parallel. Writes for one Client wait for each other; see
contended on Errors.
This read counts against the bounds it reports, at both doors.
Path parameters
string
required
The Tenancy asking.
Response
integer
required
Requests in flight at once. A
concurrency_limited refusal states it in details.bound.integer
required
How long a request beyond
concurrent waits for a slot, in milliseconds.number
required
Requests started per second. A
rate_limited refusal states it in details.bound.integer
required
Requests started at once before the rate applies.
string
required
default where you are held to the Platform’s default; tenant where you have an entry of your own.