Getting started
Programmatic access to the analytics data of your VTurb account
The VTurb Analytics API gives you programmatic access to the analytics data of your VTurb account, so you can:
- Query real-time and historical data
- Build your own reports and charts
- Bring analytics data into your own applications
- Automate data pipelines and business decisions
Getting started
- Create an account if you don't have one yet.
- Generate an API key in your dashboard.
- Send it on every request, together with the API version and a
User-Agent, as described in Authentication. - Pick the data you need from the endpoints listed in the sidebar.
Base URL
https://analytics.vturb.comRequests and responses are JSON. Queries are POST requests with a JSON body; a few lookups, such as GET /players/list and GET /quota/usage, are GET.
https://analytics.vturb.net still serves the same API, but it is deprecated and will be retired
during 2026. Point your integration at analytics.vturb.com; nothing else changes.
Dates and time zones
Unless an endpoint says otherwise, dates are sent as YYYY-MM-DD HH:MM:SS and read in the time zone given in timezone, an IANA name such as America/Sao_Paulo. Without timezone, dates are read in UTC.
{
"start_date": "2026-09-01 00:00:00",
"timezone": "America/Sao_Paulo"
}Every query only sees the players and data of the company your API key belongs to.
Responses
- A missing or invalid parameter gets
400, with anerrorthat says which one. - On most queries, a
player_idthat is not in your account gets200with zeros or an empty list, not an error. When every number comes back zero, check the ID withGET /players/list./headlines/stats_by_player,/turbo/stats_by_playerand/smart_autoplays/stats_by_playeranswer400instead. - Results are cached and refreshed in the background, so the last few minutes of activity may not show up yet.
Limits
Your company has a query quota for a time window, set by your plan and shared by all its API keys:
| Plan | Queries per minute |
|---|---|
| Basic | 60 |
| Pro | 120 |
| Scale | 300 |
| Enterprise | 800, with custom limits available |
GET /quota/usage returns your company's limits and how much of each is used. A single request may count as more than one query.
When the quota runs out, the API answers 429 Too Many Requests, with details saying which limit was reached and when it resets:
{
"error": "Query quota exceeded for this API key. Please retry in a few moments or contact support at [email protected] if this persists.",
"code": 201,
"details": {
"limit_kind": "queries",
"used": 60,
"limit": 60,
"remaining": 0,
"interval_seconds": 60,
"resets_at": "2026-04-27T12:35:00Z"
}
}limit_kind is the limit that ran out, such as queries or read_bytes, the data the queries read. Wait until resets_at before retrying, or a short while when details is missing. If your integration needs a higher limit, contact support.
Support
Code samples for each endpoint are on its page. For anything else, contact our support at help.vturb.com.