Not available yet. The authentication layer and the underlying queries are built; the
/api/v1/routes and the key management screen are not. These pages describe the planned surface and are marked where they describe a plan rather than something shipped.
Read your TrueStat data from your own code.
| Page | Covers |
| Getting an API key | Including the part where it is shown once |
| Authentication | |
| Rate limits | |
| Endpoint reference | Every endpoint and every parameter |
| Examples | Real requests and real responses |
| Errors | Every code, and what to do about each |
On every plan
The API is on both tiers, at every traffic step — Starter included. So is the CLI, and so is MCP. See Plans compared.
Your plan changes how many sites and people you have, and how far back your history goes. It does not change what you can read or how you read it.
What it is for
Three jobs, and the endpoint set is deliberately scoped to them:
Put your visitor count on your own homepage, status page or internal dashboard.
Chart your traffic in your own tool, with your own ranges and filters.
Report which AI crawlers read your site — the thing only TrueStat can answer.
What it is not for
Everything is read-only. There is no way to write an event, create a site, manage a key, invite a colleague or change a setting over the API. Site and account administration is dashboard-only, on purpose: every write endpoint is authorisation surface, and there is no demand behind these that would justify opening it.
To send events, use the tracking script.
Two things that are deliberately absent
There is no visitor endpoint. No visitor list, no per-visitor journey, no lookup by id. That is not a gap to be filled later — it needs the cross-day person identity TrueStat is built without. See What we deliberately cannot do.
There is no revenue or goals-analytics surface. Those features do not exist in the product, so they do not exist in the API.