API · inboxes

Create inbox

POST /api/v2/inboxes

Authorization

inboxes:create. Use a workspace-scoped bearer key or an authorized user session.

Parameters

Required header: Idempotency-Key (1–100 alphanumeric, underscore or hyphen characters).

Name	Type	Contract
name	string · required	1–60 characters

Request

Set INBOXIT_API_KEY in your server environment. The CLI can also use an authenticated user session.

Example

curl -X POST 'https://inboxit.wtf/api/v2/inboxes' \
  -H "Authorization: Bearer $INBOXIT_API_KEY" \
  -H "Content-Type: application/json" --data @request.json \
  -H "Idempotency-Key: request-001"

JSON body

Save this JSON as request.json for the request above. Replace example values with your own.

Example

{
  "name": "Support"
}

CLI equivalent

Use INBOXIT_TOKEN for a scoped key, or inboxit login for a user session.

Example

inboxit inboxes create --data @request.json --idempotency-key request-001

Response

HTTP 202. Example values are illustrative; excerpts are marked.

Example

{
  "id": "INBOX_UUID",
  "name": "Support",
  "address": "agent-generated@agents.inboxit.wtf",
  "status": "pending",
  "created_at": "2026-10-23T12:00:00Z"
}

Behavior & errors

Idempotency-Key required (1–100 letters/digits/_/-). Same key with different name returns 409. Provisioning runs asynchronously. Unlimited inboxes on every plan; volume and storage quotas still apply. Common errors: 400 invalid input, 401 unauthenticated, 403 insufficient permission, 404 missing/inaccessible resource, 409 conflict, 429 rate/usage limit, 503 service unavailable. See Errors & retries for recovery guidance.