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.

address_unavailable

HTTP 503 · No free address could be found (practically never happens).

Endpoints: POST /v1/signup, POST /v1/inboxes

When it happens

When	Message (as returned)	Fix (as returned)
Signup: all 5 address candidates were taken.	`Could not find a free address.`	`Retry the signup with a new challenge.`
Creating an inbox: all 5 address candidates were taken, or the address step lost 3 insert races in a row.	`Could not find a free address.`	`Retry the request.`

Headers

Retry-After: 1 on POST /v1/inboxes, only when the address step lost 3 insert races in a row. Not sent when all 5 candidates were taken, and never sent on POST /v1/signup.
Cache-Control: no-store and Content-Type: application/problem+json, as on every problem response.

What to do

Retry. For signup, get a new challenge first: the old one may already be used up.

Example

{
  "type": "https://docs.replyz.io/errors/address_unavailable",
  "code": "address_unavailable",
  "status": 503,
  "message": "Could not find a free address.",
  "fix": "Retry the signup with a new challenge.",
  "docs": "https://docs.replyz.io/errors/address_unavailable.md"
}

All codes: Errors.