Drill into a usage row
The individual events behind one row of the usage report — every resolution or message that contributed, with its price and the conversation it came from. This is how a customer answers “why is this number what it is”.
section and row_key are both required; row_key must be a key from that section’s rows, and anything else returns a 422 with type: "invalid_row_key". Paginated by cursor rather than page number.
Authorizations
This token can be obtained by visiting the profile page or via rails console. Provides access to endpoints based on the user permissions levels. This token can be saved by an external system when user is created via API, to perform activities on behalf of the user.
Path Parameters
The numeric ID of the account
Query Parameters
Which usage section to drill into.
"resolutions"
Which row within it, taken from that row's key.
"knowledge"
Events per page.
Opaque cursor from the previous page.
Named reporting window. Defaults to month.
day, week, month, quarter, year, custom "month"
Start of a custom window, ISO-8601. Required when period=custom.
End of a custom window, ISO-8601. Required when period=custom.
Response
Success
The row's events, with the same period envelope as the usage endpoint.