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.

Accounts

An account is created by signup and owns one API key and its inboxes. GET /v1/account tells the agent its status, its limits, how much it used this month, and anything that restricts it.

Statuses

Status	How an account gets it	Read mail, extract	Create or change inboxes	Delete inboxes	`wait` holds	Inbound mail
`sandbox`	Every signup. Lasts 7 days, until `expires_at`	Yes	Yes: 1 live inbox	Yes	Yes, up to 60 s	Accepted, up to 1,000 per month
`claimed`	Through the claim by a human owner, which is not available yet	Yes	Yes: 3 live inboxes	Yes	Yes	Accepted, up to 5,000 per month
`suspended`	Set by Replyz	Yes	No: `403 org_not_active`	Yes	No, answers at once	Rejected
`expired`	A `sandbox` account once its `expires_at` has passed	Yes	No: `403 org_not_active`	Yes	No, answers at once	Rejected

Today every account is a sandbox account: no account can become claimed yet.

The 7-day sandbox

expires_at is set at signup: signup time + 7 × 24 hours.
From expires_at on, the account works as expired: creating or changing inboxes answers org_not_active, wait and events?wait= do not hold, and mail sent to its addresses is rejected. Reading mail, extraction and deleting inboxes keep working.
GET /v1/account shows the stored status, which can still say sandbox after expires_at has passed. To know whether a sandbox account still works, compare expires_at with the current time.
To keep going after the sandbox, sign up again for a new account. Addresses of the old account are never issued to anyone else.

`GET /v1/account`

curl -s https://api.replyz.io/v1/account -H "Authorization: Bearer $REPLYZ_API_KEY"

{
  "org_id": "org_01M6QTC7CSG2BWBDE0CRB4H3Y7",
  "status": "sandbox",
  "agent_name": "Scout Agent",
  "created_at": "2026-11-06T06:57:41.776Z",
  "expires_at": "2026-11-13T06:57:41.776Z",
  "claim": { "claimed": false, "claimed_at": null },
  "limits": { "inboxes": 1, "receive_per_month": 1000, "send_scope": "none" },
  "usage": { "inboxes": 1, "received_this_month": 0 },
  "notices": [],
  "sending_status": "active",
  "receiving_status": "active",
  "otp_flagged_until": null
}

Field	Meaning
`status`	The stored status (see above)
`agent_name`	As sent at signup; `"agent"` if none was sent
`expires_at`	End of the sandbox
`claim`	`{claimed, claimed_at}`. Always `{claimed: false, claimed_at: null}` today
`limits`	`inboxes`: live inboxes allowed. `receive_per_month`: messages accepted per calendar month (UTC). `send_scope`: always `"none"`, the account cannot send mail
`usage`	`inboxes`: live inboxes now. `received_this_month`: messages accepted this calendar month (UTC), all inboxes together. Deleting an inbox does not lower it
`sending_status`	Informational only: there is no sending
`receiving_status`	`active` or `paused`. While `paused` (set only by Replyz), all inbound mail is rejected
`otp_flagged_until`	Set for 24 hours when the account receives an unusual volume of verification mail. While it is in the future, an account that is not `claimed` may run at most 10 extractions per UTC hour. Mail is never rejected because of it. See Limits

limits does not list every limit (for example the daily inbox-creation cap and the long-poll limit): see Limits.

Not available yet

Claiming the account by a human owner, and the /manage page for the owner. Coming soon.
Deleting the account through the API, changing agent_name, plans and billing.

Reference: GET /v1/account.