API · analytics

Retrieve analytics

GET /api/v2/analytics

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
days	query integer · optional	7, 30 or 90; default 30

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/analytics?days=30' \
  -H "Authorization: Bearer $INBOXIT_API_KEY"

CLI equivalent

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

Example

inboxit analytics get --query '{"days":"30"}'

Response

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

Example

{
  "days": 30,
  "timezone": "UTC",
  "series": [
    {
      "day": "2026-10-23",
      "sent": 2,
      "delivered": 1,
      "bounced": 0,
      "failed": 0,
      "received": 1
    }
  ],
  "totals": {
    "sent": 2,
    "delivered": 1,
    "bounced": 0,
    "failed": 0,
    "received": 1
  }
}

Behavior & errors

Example series is shortened. Workspace-scoped; outbound grouped by creation day and current status. Also returns open_tracked, click_tracked, opened, clicked, opens and clicks in totals and series, plus up to 100 recent emails with per-link counts. opened/clicked count unique emails; opens/clicks count events. Rates use tracked emails as denominators. Events are grouped by email creation day, not event day. Proxies/scanners can inflate counts; image blocking can hide opens. Native provider failures may count as failed instead of bounced. 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.