Read-only programmatic access to events, logs, and sessions. Built for CI pipelines, AI agents, and custom integrations that need data without the Dashboard.
01Overview
Every request authenticates with a bearer token minted under Settings → API Tokens.
Base URLhttps://api.sumidata.io
AuthAuthorization: Bearer sumi_live_…
Content-Typeapplication/json
ScopeRead-only — no event ingest here
i
Tokens are scoped to a single project. Project filtering is applied automatically from the token — never pass projectId in query params.
!
The Partner API is read-only. To send events from a backend, use POST /sdk/ingest (the SDK ingest endpoint, authenticated by projectId in the JSON body — no Bearer token).
02Query DSL
All list endpoints share the same filter syntax.
The pattern is q[field__action]=value. Multiple filters combine with AND.
Filter actions
Action
SQL
Example
__eq
= value
q[level__eq]=error
__not
!= value
q[source__not]=sdk
__in
IN (...)
q[level__in]=error,warn
__like
ILIKE '%v%'
q[name__like]=page
__gte
>= value
q[timestamp__gte]=2026-01-01
__lte
<= value
q[timestamp__lte]=2026-04-01
__is
IS NULL
q[sessionId__is]=null
__order
ORDER BY
q[timestamp__order]=desc
Pagination
q[page] (default 1) and q[perPage] (default 50, max 200).
03Endpoints
Four endpoints — health, events, logs, sessions. All read-only GETs.
Conversion fields (orderId, totalAmount, productId, utmSource…) are columns on the same row, not inside payload. Request them explicitly via q[orderId__not]= to list conversions, or filter by name. payload contains only the free-form fields you sent — metadata (_category/_feature/_surface) is stripped into the per-project dictionary at ingest.