Get Usage
Returns metered spend for the project over a date window, broken down by day, app, and upstream service. This is the cost side of the ledger. See Get Balance Transactions for how that spend drew down the credit balance.
Authorization
Authorization In: header
Path Parameters
ID of the project to report usage for.
Query Parameters
Start of the window as a YYYY-MM-DD date, inclusive and read in UTC.
End of the window as a YYYY-MM-DD date, inclusive and read in UTC.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/projects/string/analytics/usage"{ "meta": [ { "name": "string", "type": "string" } ], "rows": 0, "statistics": { "bytes_read": 0, "elapsed": 0, "rows_read": 0 }, "usage": { "cost": 0, "duration": 0, "metricCount": 0 }, "data": [ { "app": "string", "cost": 0, "date": "string", "service": "string" } ]}Get Funnel Steps By Day
The same sequential funnel as Get Funnel Steps, but broken out per day so you can chart step conversion over time. Returns one row per step per day.
List Contacts
Queries contacts with attribute and event filters, returning a page of contacts plus the total `count` matching the filter. A POST because the filter structure is too rich for a query string. This is the endpoint behind audience building. The same filter shape defines a dynamic contact list or a campaign audience.