Usage and cost
Metered usage and its cost for a billing period: meters, totals (rated,
not yet rated, credit, due) with a projection for the current month, a
daily breakdown, every template, and the period’s sandboxes, most
expensive first, a page at a time.
Dashboard sessions of any role; API keys with the usage:read scope.
sandboxes holds limit rows (50 unless you pass it, at most 1000).
sandboxCount is how many sandboxes had usage in the period, on every
page. While more remain the response carries nextCursor: pass it back
as cursor, with the same period, for the next page. A closed
period pages the same way every time; in the current month costs are
still moving, so a sandbox can change pages between requests. To read
one sandbox’s row wherever it ranks, pass sandboxId instead.
Usage arrives a minute at a time: a minute is included within about 35 seconds of its end, so the minute a sandbox was deleted in shows up that long after the minute is over, not at the delete. Read again after that before comparing running time with a sandbox’s lifetime.
Authorizations
Query Parameters
Response
The usage document.
The month against what the plan includes, on the allocated rate card (absent for months before the current plans). vCPU-hours each include 2 GiB-hours of memory; storage is never included. On this rate card totals.dueUsd is overageUsd for a plan that bills it and 0 for Free, which stops instead.