twelvebit API
API by twelvebit · rest
Read analytics, push the tracking plan (analytics.yaml), and send server-side events. Authentication. Send Authorization: Bearer <key>. A site key (tbk_…) reads and writes one site, and ignores ?site=. An account token (tbt_…) reaches every site of its user; name the site with ?site= (site id, public id tb_…, or domain). A Better Auth session (cookie, or the session token as a Bearer) works like an account token. Create keys in the site settings or on /account, or run npx twelvebit init. Scopes. Each key has scopes, and each operation names the one it needs in x-required-scope. A key without it gets 403 insufficient_scope with required_scope and key_scopes. Keys made before scopes existed have read, write:events and write:config. Sessions have every scope. The site role still applies: viewers never write, and only owners manage the team or delete a site. | Scope | Allows | |---|---| | read | Read analytics, revenue, ad spend and campaign…
Endpoint: https://twelvebit.app/
Verification: observed. Source: crawl.
Capabilities (68)
- List alerts
- Create an alert
- Alert delivery history
- Get an alert
- Change an alert
- Delete an alert
- List annotations
- Add an annotation
- Get an annotation
- Change an annotation
- Delete an annotation
- The account's plan usage and limits
- Make a checkout link (or change the plan)
- Crawler traffic
- Record a crawler hit
- Top values of one dimension
- Find or create a site and mint a key (CLI)
- Send a goal from your server
- Start the browser extension's sign-in
- Finish the browser extension's sign-in
- Sign the browser extension out
- List or compute funnels
- Save a funnel
- Get a saved funnel
- Change a saved funnel