Skip to content
Replyz docs
Not available yet. Replyz is built and tested, but not deployed: https://api.replyz.io is the planned address and does not answer yet. These pages describe the API as it is built today and may change before launch.

unauthorized

HTTP 401 · The API key is missing, malformed, unknown or revoked.

Endpoints: Every route that needs a key

When it happens

Section titled “When it happens”
When Message (as returned) Fix (as returned)
The Authorization header is missing, is not Bearer <token>, or the token is not in key format (rz_live_ + 32 letters and digits). Missing or malformed API key. Send the header Authorization: Bearer rz_live_… with the api_key from POST /v1/signup.
The key is unknown or revoked (the same answer for both; it does not say whether a key ever existed). Unknown or revoked API key. Use your current key. The human owner can issue a new one at https://replyz.io/manage.

Headers

Section titled “Headers”
  • WWW-Authenticate: Bearer realm="replyz".
  • Cache-Control: no-store and Content-Type: application/problem+json, as on every problem response.

What to do

Section titled “What to do”
  • Send Authorization: Bearer <api_key> with the key from the signup response. A key in the query string or the body is not read.
  • A lost key cannot be recovered.

Example

Section titled “Example”
{
  "type": "https://docs.replyz.io/errors/unauthorized",
  "code": "unauthorized",
  "status": 401,
  "message": "Missing or malformed API key.",
  "fix": "Send the header Authorization: Bearer rz_live_… with the api_key from POST /v1/signup.",
  "docs": "https://docs.replyz.io/errors/unauthorized.md"
}

See also

Section titled “See also”

All codes: Errors.