For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
GuidesWhite-labelAPI Reference
GuidesWhite-labelAPI Reference
  • Panic API Reference
    • Errors & status codes
LogoLogo
On this page
  • Status codes
  • Handling errors

Errors & status codes

Was this page helpful?
Previous
Built with

The Panic API uses standard HTTP status codes to indicate the result of a request: 2xx for success, 4xx for client errors, and 5xx for server errors. Error responses include a message describing the problem.

Status codes

CodeMeaning
200 OKThe request succeeded and the expected data was returned.
201 CreatedA new resource was created, such as a customer or subscription.
204 No ContentThe request succeeded with no response body.
400 Bad RequestThe request was malformed — missing fields, bad formatting, or invalid values (for example, a blank mobile number on registration).
401 UnauthorizedAuthentication is missing or invalid. Check the clientId, clientSecret, or bearer token.
403 ForbiddenAuthenticated, but not permitted — for example, raising a callout for a customer without an active subscription.
404 Not FoundThe resource doesn’t exist or isn’t visible to your customer source. Check the path and identifiers.
409 ConflictThe request conflicts with current state, such as a duplicate customer or an already-active subscription.
500 Internal Server ErrorAn unexpected server-side error.
502 Bad GatewayAn upstream service returned an invalid response; retry shortly.

Handling errors

  • Read the response message for a human-readable explanation.
  • Treat 5xx (and 502) as transient — retry with backoff.
  • Treat 4xx as actionable — fix the request or the resource state before retrying.