GET /usages

Retrieves the list of usages.

Servers

Request headers

Name Type Required Description
chargebee-request-origin-device String No

The device from which the customer has made the request

chargebee-business-entity-id String No

If the site has multiple business entities, you can use this custom HTTP header to specify the business entity for which Chargebee should perform the operation.

chargebee-request-origin-user String No

The email address of your customer/user. Use this when the email address has only ASCII characters.

chargebee-request-origin-ip String No

The IP address of the customer where the request originated

chargebee-request-origin-user-encoded String No

The Base64-encoded email address of your customer/user. Use this if the email address has UTF-8 characters. When this header is provided, the header chargebee-request-origin-user is ignored.

Query parameters

Name Type Required Description
id Object No

optional, string filter
A unique and immutable id for the usage. If not provided, it is autogenerated.
Supported operators : is, is_not, starts_with

Example → id[is] = "usage_lsfja24411"

source Object No

optional, enumerated string filter
The source from which the usage record was created. Possible values are : admin_console, api, bulk_operation.
Supported operators : is, is_not, in, not_in

Example → source[is] = "api"

limit Integer No

The number of resources to be returned.

Default value: 10

usage_date Object No

optional, timestamp(UTC) in seconds filter
The time at which this usage occurred. Chargebee bills only those usages whose usage_date falls within a time when the subscription status was active or non_renewing. However, the remaining usage records are still stored and are retrievable.
Note: If usage_date corresponds to a time already invoiced, then it is stored but never invoiced unless the invoice is regenerated.
Supported operators : after, before, on, between

Example → usage_date[after] = "1601220958"

invoice_id Object No

optional, string filter
When the usage has been invoiced, this is the id of the invoice. This is cleared when the invoice is voided or deleted.
Supported operators : is, is_not, starts_with, is_present

Example → invoice_id[is] = "null"

item_price_id Object No

optional, string filter
The id of the item price to which this usage belongs. The item price must be a part of the subscription or should have been part of it historically.
Supported operators : is, is_not, starts_with

Example → item_price_id[is] = "sprout"

sort_by Object No

optional, string filter
Sorts based on the specified attribute.
Supported attributes : usage_date
Supported sort-orders : asc, desc

Example → sort_by[asc] = "usage_date"
This will sort the result based on the 'usage_date' attribute in ascending(earliest first) order.

offset String No

Determines your position in the list for pagination. To ensure that the next page is retrieved correctly, always set offset to the value of next_offset obtained in the previous iteration of the API call.

subscription_id Object No

optional, string filter
The id of the subscription to which this usage record belongs.
Supported operators : is, is_not, starts_with

Example → subscription_id[is] = "active2"

updated_at Object No

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.