customers
Customer Usage Route
How this person used the product: their flow, session by session.
Reads our own event store rather than PostHog, so this is a handful of indexed selects and stays inside the profile's load budget. The two workspace-level comparisons it draws on (the per-event baseline and the dominant path) are precomputed snapshots; when they are missing the tab drops the comparison and shows the flow, rather than blocking on a scan.
get/api/v1/customers/{customer_id}/usage
Path parameters
customer_idstring uuid required
Query parameters
daysinteger
sessionsinteger
Headers
authorizationstring nullable
Bearer <token>
Bearer <token>
Response
Successful Response
Changes
No recorded changes to this endpoint across all 1 revision of this API.