Billing API, REST: BillingAccount.list
Retrieves the list of billing accounts available for current user.
HTTP request
GET https://billing.api.il.nebius.cloud/billing/v1/billingAccounts
Query parameters
Parameter | Description |
---|---|
pageSize | The maximum number of results per page to return. If the number of available results is larger than pageSize, the service returns a nextPageToken that can be used to get the next page of results in subsequent list requests. The maximum value is 1000. |
pageToken | Page token. To get the next page of results, set pageToken to the nextPageToken returned by a previous list request. The maximum string length in characters is 100. |
Response
HTTP Code: 200 - OK
{
"billingAccounts": [
{
"id": "string",
"name": "string",
"createdAt": "string",
"countryCode": "string",
"currency": "string",
"active": true,
"balance": "string"
}
],
"nextPageToken": "string"
}
Field | Description |
---|---|
billingAccounts[] | object List of billing accounts. |
billingAccounts[]. id |
string ID of the billing account. |
billingAccounts[]. name |
string Name of the billing account. |
billingAccounts[]. createdAt |
string (date-time) Creation timestamp. String in RFC3339 text format. The range of possible values is from To work with values in this field, use the APIs described in the Protocol Buffers reference. In some languages, built-in datetime utilities do not support nanosecond precision (9 digits). |
billingAccounts[]. countryCode |
string ISO 3166-1 alpha-2 country code of the billing account. |
billingAccounts[]. currency |
string Currency of the billing account. Can be one of the following:
|
billingAccounts[]. active |
boolean (boolean) Represents whether corresponding billable objects can be used or not. |
billingAccounts[]. balance |
string Current balance of the billing account. |
nextPageToken | string This token allows you to get the next page of results for list requests. If the number of results is larger than pageSize, use nextPageToken as the value for the pageToken query parameter in the next list request. Each subsequent list request will have its own nextPageToken to continue paging through the results. |