Skip to main content
Start with the response’s Content-Type. For JSON, read code and the endpoint’s documented text field (error or message). Use the code to choose a recovery action and keep a fallback for an unfamiliar code. Messages may vary. Braces in an endpoint’s response text mark values filled in for each request. If you already have a code, jump to authentication and requests, gacha and settlement, marketplace or redemption. Use the HTTP status and machine-readable code to choose a recovery action. The text in error or message can vary. On a successful HTTP response, inspect the operation’s status or stream event first.

Two ways to get HTTP 429

List pack contents can return either of these JSON bodies. If the catalog is busy, wait for the interval in Retry-After when present.
If the builder key has reached its request limit, reduce the request rate for that key.
When you contact Renaiss about a failure, include the HTTP status, error code and the x-request-id response header. For an accepted pull or buyback, also include the requestId returned in the response body.

Responses without a code

Check Content-Type before parsing the body. A plain-text error has no JSON code. When a throttled catalog read or busy direct buyback returns Retry-After, wait the number of seconds shown.

Failures after a request is accepted

Authentication and request errors

Gacha, funding and settlement

Marketplace orders

Physical redemption