Skip to main content
Live. These reports are shipped and available in your workspace. The endpoint paths and response shapes below match the current API. A few individual metrics aren’t wired to a data source yet and return a constant 0 (for example pushViewRate and conversions); each is called out inline where it appears.
Analytics reports turn the data already in your workspace, on-chain holdings, contacts, delivery events, and automation runs, into the cards you see on the analytics dashboard. Each report is a read-only endpoint; nothing here sends, mutates, or spends credits.

​
The reports

Holder distribution

How token holdings spread across wallets, the top holders, and concentration.

Retention cohorts

Weekly signup cohorts and the curve of how many stay engaged.

Engagement by segment

Per-segment email sent, open, and click rates.

Campaign report

Per-campaign delivery and engagement, one row per run.

Automation performance

Per-flow enrolments, completion rate, and downstream engagement.

​
Access model

Every report lives under the base path https://api.onchainsuite.com/api/v1/analytics/reports and is session-authenticated, the same cookie session your dashboard uses, scoped to your active organization. They are read-only, so every role, including Viewer, can run them.
These are dashboard reports, not part of the sk_ server-to-server surface. They authenticate with your dashboard session and the active-organization context, not a secret key. For programmatic access to your data from a backend, use the SQL schema and the server-to-server API.

​
Response format

Like the rest of the platform, each response is wrapped in the standard envelope; the report body is the contents of data.
A request with no active organization selected returns 400 No active organization selected.