HTTP Read API

Takt exposes an HTTP Read API to query a site’s statistics from a program or an agent. It reuses the /api/v1/sites/{domain}/stats/* endpoints and authenticates with an API key (no session cookie).

Authentication

Create an API key with the stats:read permission from your org settings, then pass it in the Authorization header:

curl -H "Authorization: Bearer takt_sk_xxx" \
  "https://app.taktlytics.com/api/v1/sites/example.com/stats/summary?from=2026-03-01T00:00:00Z&to=2026-03-08T00:00:00Z"

A key is bound to a single site. An invalid key returns 401; a key missing the right permission or targeting another domain returns 404 (anti-enumeration).

Endpoints

Most read routes live under /api/v1/sites/{domain}/stats/: summary, timeseries, breakdown, realtime, goals, funnels, properties, revenue. CSV/JSON export uses a distinct path, /api/v1/orgs/{org}/sites/{domain}/stats/export, with the same key authentication. The detailed contract (parameters, response schemas) is described in the OpenAPI specification (api/openapi.yaml).

Quotas & billing

Read API access is part of your plan’s API/AI add-on, metered as a number of requests per month. Each successful read request counts as 1 unit. Rejections (invalid key, quota exceeded, wrong domain) are not counted.