Skip to main content
AuthFlame uses conventional HTTP status codes and returns a JSON error envelope on failure. Handle errors defensively: never block signups because AuthFlame is briefly unreachable, but do fail closed on clear authentication problems.

Status codes

Error envelope

Errors return a JSON body with a stable shape:
  • error.code: a short, machine-readable string you can branch on.
  • error.message: a human-readable description. Do not surface this directly to end users.

Handling errors in your signup flow

1

Distinguish user errors from platform errors

Treat 4xx responses as problems with the request (fix your integration or the input). Treat 5xx and network errors as transient AuthFlame issues.
2

Fail closed on auth errors

A 401 or 403 means your integration is misconfigured. Log the incident and stop sending traffic with that key until it is fixed.
3

Fail open on transient errors

For 5xx responses and timeouts, decide up front whether to allow the signup, queue it for later review, or fall back to a lightweight local check. Blocking every signup during an outage is usually the wrong tradeoff.
4

Back off on 429

Respect 429 responses with exponential backoff. Bursting signups in a loop will keep you rate limited longer.