Build on your analytics

A REST API over everything Rybbit collects: query any metric, ingest events from any platform, and pull raw data into your own systems. Prototype it all in the built-in playground.

api

Your analytics shouldn't be locked inside a dashboard. The Rybbit API exposes everything the dashboard shows as REST endpoints: overview stats, time series, breakdowns, sessions, user profiles, goals, funnels, errors, Web Vitals, and raw events. Build reports, internal tools, and product features on live data.

It works in both directions. Read endpoints power custom dashboards, scheduled digests, and warehouse syncs. The track endpoint ingests events from anywhere (backends, mobile apps, webhooks, CLI tools), with geolocation and user-agent parsing handled for you, and API-key requests trusted past bot detection. Management endpoints automate the rest: sites, members, teams, goals, and imports.

Start without writing code: the API Playground built into your dashboard lets you browse endpoints, adjust parameters visually, watch live responses with your own data, and copy working snippets. Authenticate with organization or personal keys, optionally restricted to just the permissions an integration needs.

What you can do

Query every metric

Overview KPIs, time series, breakdowns by any dimension, sessions, user profiles, events, goals, funnels, errors, Web Vitals, retention, journeys, even bot traffic. If the dashboard shows it, an endpoint returns it.

Server-side event ingestion

POST pageviews, custom events, errors, and performance data from your backend, mobile app, or anything that speaks HTTP. Rybbit resolves geolocation and parses user agents for you.

Built-in API Playground

Browse every endpoint in your dashboard, tweak parameters visually, see live responses with your own data, and copy ready-to-use code snippets.

Raw data access

Pull raw events and sessions (newest first, filterable, paginated) to sync your analytics into a warehouse or join it with your product data.

Organization & personal keys

Organization keys access every site in the org and survive team changes, which makes them the right choice for integrations. Personal keys have exactly your access. Both can be restricted to specific permissions and revoked anytime.

Full management surface

Create sites, invite members, manage teams, define goals and funnels, and run data imports programmatically. You can automate provisioning end to end.

How it works

1. Create an API key
   Generate an organization key in Settings → Organization for integrations, or a personal key in Settings → Account for scripts. Optionally restrict either to specific permissions.

2. Prototype in the Playground
   Open API Playground from your site's sidebar. Pick an endpoint, set parameters with visual controls, and watch live responses come back with your real data.

3. Copy the code and call the API
   The Playground generates ready-to-use snippets. Authenticate with a Bearer token and use the same time ranges and filters the dashboard uses.

4. Ship it
   Scheduled reports, internal dashboards, warehouse syncs, user-facing stats in your own product: anything that can make an HTTP request can build on your analytics.

Who uses this

Product engineers

Surface analytics inside your own product: show creators their post views or customers their campaign stats, powered by live Rybbit data.

Data teams

Sync raw events into your warehouse on a schedule and join web analytics with product and revenue data.

Agencies

One organization key covers every client site. Generate weekly reports across your whole portfolio automatically.

Backend & mobile developers

Track events where a script tag can't run: server-rendered flows, mobile apps, payment webhooks, CLI tools.

SaaS platforms

Provision a site per customer, manage access programmatically, and offer analytics as part of your own product.

Marketing engineers

Pipe channel performance and conversion data into Slack digests, spreadsheets, and the tools your team already reads.

Frequently asked questions

How is the API different from the MCP server?

Can I send events through the API as well as read data?

Should I use an organization key or a personal key?

What are the rate limits?

Is the API stable?

Can I explore the API without writing code?

Your data, your code

Every metric as an endpoint, event ingestion from any platform, and a playground to prototype in.