Skip to main content
Every error response carries a stable code you can match on, a type that groups codes, and a request_id to quote when you contact support. The same value is in the X-Request-ID response header. The doc_url field links to the entry for that code on this page.
Match on code, not on message. Messages can change. Some errors also carry param (the field at fault), fields (one entry per invalid field), or details. A validation_error lists every failing field in fields in one response.

Retry rules

Invalid request

The request is malformed or breaks a rule on its own. Fix the request and send it again. Type: invalid_request.

Authentication

Scrip could not tell who is calling. Type: authentication.

Permission

Scrip knows who is calling, and that caller cannot do this. Type: permission.

Not found

The resource does not exist, or no longer exists. Type: not_found.

Conflict

The request is valid but conflicts with the current state of a resource. Read the resource, then decide whether to retry. Type: conflict.

Unprocessable

The request is well formed and breaks a business rule. Type: unprocessable.

Rate limited

You sent requests faster than the limit allows. See Limits and durations. Type: rate_limited.

Server and upstream

Something failed on the Scrip side or at a service Scrip depends on. Retry with backoff. Type: internal.