Skip to main content
GET
Get organisation usage

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

from
string<date>

First UTC day to read, YYYY-MM-DD. Defaults to the first day of the current month. Not after today, and not more than 400 days back (how long usage is kept).

to
string<date>

The day after the last UTC day to read, YYYY-MM-DD. Defaults to tomorrow. At most 93 days after from; a longer stretch is read in parts.

granularity
enum<string>
default:month

Period length of each line.

Available options:
month,
day
group_by
enum<string>
default:meter

Split the lines by meter only, or also by cluster, by the application a managed service serves, or by managed service instance. Meters not attributed to the grouping keep one organisation line.

Available options:
meter,
cluster,
application,
instance

Response

The usage report.

What the organisation used of Ankra over a window, one line per meter, period and group. Usage nobody measured is never shown as zero: a line whose every hour was unmeasured is unknown and has no quantity, and one measured in part is partial and its quantity a lower bound. Only a line Ankra has a published rate for carries an amount; during the managed services pilot nothing else is billed (Terms clause 8.8).

from
string<date-time>
required

Start of the window: midnight UTC of the first day read.

to
string<date-time>
required

End of the window: midnight UTC after the last day read, or the time of the request when that is earlier - usage that has not happened is not reported.

granularity
enum<string>
required

The length of each line's period: a calendar month or a UTC day, cut to the window at either end.

Available options:
month,
day
group_by
enum<string>
required

What the lines are split by. The per-instance and per-application reads are always split by instance.

Available options:
meter,
cluster,
application,
instance
lines
object[]
required

Ordered by meter, then group, then period. Grouped by meter, every meter answers every period, even with nothing used. Grouped by cluster, application or instance, a group that used none of a meter in a period it was fully measured has no line.