TinyAnalytics API Reference

TinyAnalytics has two separate developer surfaces:

Surface	Use it for	Authentication
Browser API	Pageviews, custom events, revenue, errors, user identity, traits, groups, flags, and replay consent.	No API key. The installed snippet supplies the site ID.
HTTP data API	Reading analytics, running scoped SQL, and managing sites and analytics configuration.	API key as `Authorization: Bearer <key>`.

Visitor measurement is client-side. Install the tracking script, then use the browser event API and browser identity API instead of building a separate ingestion client.

HTTP data API base URL

Authenticated data and management endpoints use:

https://dash.tinyanalytics.io

The HTTP API covers 155 published endpoints across 30 groups. You can read reports, manage sites, define goals and funnels, read heatmaps, drive feature flags and experiments, run surveys, build dashboards, configure alerts and scheduled reports, and operate uptime monitors. Every published endpoint has its own page in the Endpoint reference section.

Authenticate data API requests

Create an API key in Settings → Account, then send it in the Authorization header. Reads and management use the key owner’s organization, role, and team access.

curl https://dash.tinyanalytics.io/api/sites/1/overview \
  -H "Authorization: Bearer YOUR_API_KEY"

await fetch("https://dash.tinyanalytics.io/api/sites/1/overview", {
  headers: { Authorization: "Bearer YOUR_API_KEY" },
})

import requests

requests.get(
    "https://dash.tinyanalytics.io/api/sites/1/overview",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
)

Never expose an API key in browser code, a public bundle, or a URL. The browser tracking API does not need one.

If an AI agent is doing the work, the MCP server exposes the data and management surface as tools for Claude Code, Cursor, VS Code, and Codex CLI.

Response conventions

Successful reads return 200 with a JSON body. List endpoints generally return an object with a data array. Common status codes:

Code	Meaning
`200`	The read or management request succeeded.
`400`	The request contains an invalid field or parameter.
`401`	The API key is missing or invalid.
`403`	The key owner cannot access the resource, or a restricted key lacks the required grant.
`404`	The requested resource does not exist or is not visible to the key owner.
`429`	A documented security or tool-specific rate limit was exceeded.

Frequently asked questions

How do I send an event from my site?

Install the tracking script and call window.tinyanalytics.event() in the browser. Browser collection is keyless; see the browser event API.

Can I put an API key in my frontend?

No. API keys grant access to private analytics and management capabilities. Keep them out of frontend code and use the keyless browser API for visitor measurement.

Where do I find the full endpoint list?

Browse Endpoint reference in the sidebar or use the in-product API playground, which generates examples for the current endpoint registry.

Browser event API

Send pageviews and custom events from client-side code.

Browser identity API

Identify users and update traits from client-side code.

Analytics read API

Read overview, time-series, breakdown, session, and event data.

API keys

Create a least-privilege credential for data and management calls.

API playground

Browse and generate examples for published endpoints.

Start here

Browser APIs

Data API

Authentication & tools

Endpoint reference

TinyAnalytics API Reference

HTTP data API base URL

Authenticate data API requests

Response conventions

Frequently asked questions

Browser event API

Browser identity API

Analytics read API

API keys

API playground

​HTTP data API base URL

​Authenticate data API requests

​Response conventions

​Frequently asked questions

​Related

Browser event API

Browser identity API

Analytics read API

API keys

API playground

HTTP data API base URL

Authenticate data API requests

Response conventions

Frequently asked questions

Related