Read the usage ledger
Changed onA page of the account's usage ledger, newest first, with the filters applied to that page: a filtered page can hold fewer entries than limit, or none, while has_more is true. Page with cursor until it is false.
Request
- Base URLhttps://api.sparkvault.com/v1
- Auth
- API key in header X-API-Key
- or HTTP bearer
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Query parameters
A page-size hint: a value above 1000 reads as 1000, and a missing, zero, negative or non-numeric one as 1000.
The next_cursor a previous page returned, with the same start_date, end_date, type and category. Opaque, and sealed to the query that issued it.
Only entries of this type (e.g. spark_create). Ignored with a YYYY-MM-DD start_date.
Only entries counted under this usage category, as GET /billing/summaries names it.
The range's start: a Unix timestamp, or a YYYY-MM-DD date (UTC).
The range's last day (YYYY-MM-DD, UTC), with a YYYY-MM-DD start_date only. Omitted: the start's day.
Response
A page of the ledger.
Changes
- info
added the new optional
queryrequest parametercategory - info
added the new optional
queryrequest parametercursor - info
added the new optional
queryrequest parameterend_date - info
added the new optional
queryrequest parameterlimit - info
added the new optional
queryrequest parameterstart_date - info
added the new optional
queryrequest parametertype - info
added the non-success response with the status
- info
added the success response with the status
- info