Errors and limits
Error format
Section titled “Error format”Errors are application/problem+json (RFC 9457) with a stable code:
{ "type": "https://api.uptools.io/trustorder/problems/invalid-request", "title": "Bad Request", "status": 400, "detail": "email_hash must be 64 lowercase hex characters", "code": "INVALID_REQUEST"}detail never contains the data you sent.
| Status | code |
Meaning |
|---|---|---|
| 400 | INVALID_REQUEST |
invalid JSON, unknown field, wrong type or a hash that is not 64 lowercase hex characters |
| 401 | UNAUTHORIZED |
missing, wrong, unknown or revoked key |
| 403 | FORBIDDEN |
the account is suspended or the webshop is disabled |
| 404 | NOT_FOUND |
no such report or exception |
| 409 | INVALID_REQUEST |
a voided report cannot be withdrawn |
| 413 | PAYLOAD_TOO_LARGE |
the request is too large |
| 429 | RATE_LIMITED |
too many requests; wait as Retry-After says |
| 429 | QUOTA_EXCEEDED |
the daily check quota is used up |
| 503 | INTERNAL |
a temporary error on our side |
On any error at checkout, let the order through (fail open).
Limits
Section titled “Limits”- Rate: each key can send 20 requests per second, with bursts of 40. Above that the answer is
429 RATE_LIMITEDwithRetry-After: 1. A batch of signals uses one unit per 50 rows. - Daily checks:
POST /checkhas a daily quota per webshop and environment, counted per UTC day; the default is 50,000.GET /meshows the quota and today’s count. Above it the answer is429 QUOTA_EXCEEDED. - Request size: 64 KiB, and 1 MiB for
POST /signals/batch. - Key changes: revoking a key, or suspending an account, takes effect within 60 seconds.