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.

name_reserved

HTTP 400 · The name would make a reserved address.

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

When it happens

When	Message (as returned)	Fix (as returned)
Signup: the slug made from `agent_name` is reserved. Checked before the proof of work, so the challenge stays valid.	`That agent_name is reserved (role words, brand names and look-alikes).`	`Choose a different agent_name (your challenge is still valid), e.g. your own name for the agent.`
Creating an inbox: the slug made from `name` (or, without `name`, from the account’s `agent_name`) is reserved.	`That name is reserved.`	`Send a different "name" (it becomes the start of the address).`

What to do

Pick another name. At signup you can send the same challenge and nonce again with the new agent_name: the proof of work does not include the name.

Example

{
  "type": "https://docs.replyz.io/errors/name_reserved",
  "code": "name_reserved",
  "status": 400,
  "message": "That agent_name is reserved (role words, brand names and look-alikes).",
  "fix": "Choose a different agent_name (your challenge is still valid), e.g. your own name for the agent.",
  "docs": "https://docs.replyz.io/errors/name_reserved.md"
}

See also

Inboxes

All codes: Errors.