API · logs

List logs

GET /api/v2/logs

Authorization

emails:read. Use a workspace-scoped bearer key or an authorized user session.

Parameters

All resource access is checked against the selected workspace and user permissions.

Name	Type	Contract
status	query enum · optional	all, pending, queued, delivered, bounced, failed, uncertain, received
limit	query integer · optional	1–100, default 50
before	query string · optional	Opaque next cursor from previous response

Request

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

Example

curl -X GET 'https://inboxit.wtf/api/v2/logs?status=all&limit=50' \
  -H "Authorization: Bearer $INBOXIT_API_KEY"

CLI equivalent

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

Example

inboxit logs list --query '{"status":"all","limit":"50"}'

Response

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

Example

{
  "items": [],
  "next": null
}

Behavior & errors

Items: id, email_id, status, recipient, subject, created_at, delivered_at, failure_code, attempts. Incoming email_id/subject can be null. Newest first; next=null ends pagination. No message bodies. 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.