Data from the past hour may not reflect the full set of statistics. For the most complete and accurate results, we recommend accessing the data at least one hour after the relevant time period. Updates are generally available within a 24-hour window, though timing can vary. Scheduled maintenance or other exceptions may occasionally cause delays beyond 24 hours.
API key for authentication. Make sure to include the word apikey, followed by a single space and then your token.
Example: apikey 1234$abcdef
The start date of the report period (ISO 8601). The report starts from the beginning of this day in UTC.
The end date of the report period (ISO 8601). The report ends just before the beginning of this day in UTC.
Expenses for the last specified day are taken into account. As the default, False.
The response resources limit. Defaults to 10.
The response resources offset.
x >= 0List of project IDs
[16, 17, 18, 19, 20]List of region IDs.
Extended filter for field filtering.
{
"field": "flavor",
"type": "instance",
"values": ["g1-standard-1-2"]
}List of sorting filters (JSON objects) fields: project. directions: asc, desc.
Filter by tags
List of resource types to be filtered in the report.
Resource types for prebilling report
ai_cluster, ai_virtual_cluster, backup, baremetal, basic_vm, containers, dbaas_postgresql_connection_pooler, dbaas_postgresql_cpu, dbaas_postgresql_memory, dbaas_postgresql_public_network, dbaas_postgresql_volume, egress_traffic, external_ip, file_share, floatingip, functions, functions_calls, functions_traffic, image, inference, instance, load_balancer, log_index, snapshot, volume OK
Total count of the resources
x >= 0These properties are common for all individual AI clusters in all cost and usage reports results (but not in totals)