Skip to main content
The Query API gives you the reports of the dashboard and the MCP server as plain HTTP endpoints. Use it to pull your numbers into a script, a spreadsheet or your own tools. Each endpoint uses the same report code as the MCP tool or the dashboard report, so the numbers match.

Authentication

Use an API key (mana_api_...) in the Authorization header:
  • The key works on its own project only. A key of another project gets 404.
  • The key needs the scope of the endpoint. Without it, the response is 403 FORBIDDEN, and the message names the scope.
  • Call the API from a server. A request with a browser Origin header gets 403.
  • The key shares its rate limits with the MCP server: 120 requests per minute per key, and 600 per minute per workspace.

Endpoints

Every path starts with /v0/projects/{projectId}.

Filters

The report endpoints take the same filters:
  • date_from and date_to as YYYY-MM-DD (UTC). The default is the last 30 days. A range is at most 367 days.
  • Context filters, for example utm_source, channel_type, country, device and page_path.
  • filters: operator filters as { "field", "op", "value" } objects, combined with AND. On a GET endpoint, send them as a JSON array in the query string. On a POST endpoint, send them as an array in the body.
Parameters that an endpoint does not list are ignored.

Responses

A report returns the resource with no envelope:
  • date_from and date_to are the range of the report, also when you leave them out.
  • rows are the report rows.
  • totals (event timeseries only) has the totals for the range.
  • notes has fixed sentences on how to read the session columns, when a filter changes them.
Errors use the error format. Bad input gets 400 INVALID_QUERY, and the message names the parameter.

OpenAPI

The API reference pages come from an OpenAPI 3.1 document. The API code generates it from the same schemas that check each request, so the reference and the API stay the same. It covers the events, profile properties and Query API endpoints.