Sample - Stripe API
GET/v1/billing/meters/{id}/event_summaries

List billing meter event summaries

Lists aggregated event summaries for a billing meter and customer over a specified time range. Supply start_time and end_time on minute boundaries, and use value_grouping_window to request hourly or daily aggregation; summaries are generated asynchronously.

  • RetriesRetries up to 2×, 500ms backoff, 30s timeout.

9 parameters
idstringrequired
The unique identifier of the billing meter.
customerstringrequired
The unique identifier of the customer whose meter event summaries to retrieve.
end_timeintegerrequired
The exclusive end of the aggregation range as a Unix timestamp; it must align with a minute boundary.
ending_beforestringoptional
A cursor identifying an object before which to retrieve the previous page of results.
expandarray<string>optional
Fields to expand in the response.
limitintegeroptional
The number of summaries to return. Must be between 1 and 100; defaults to 10 when omitted.
start_timeintegerrequired
The inclusive start of the aggregation range as a Unix timestamp; it must align with a minute boundary.
starting_afterstringoptional
A cursor identifying an object after which to retrieve the next page of results.
value_grouping_windowstringoptional
The aggregation granularity: `day` or `hour`. Hourly ranges must align with hour boundaries, and daily ranges must align with UTC day boundaries.
Allowed:dayhour

2 status codes
200Returns a list object containing billing meter event summaries, a pagination indicator, the list object type, and the access URL.
dataarray<BillingMeterEventSummary>required
has_morebooleanrequired
True if this list has another page of items after this one that can be fetched.
objectstringrequired
String representing the object's type. Objects of the same type share the same value. Always has the value `list`.
Allowed:list
urlstringrequired
The URL where this list can be accessed.
defaultReturns an error object containing details about the failed request.
errorobjectrequired

Error handling

customer, start_time, end_time, and id must be provided. start_time and end_time must be Unix timestamps aligned with minute boundaries, and limit must be between 1 and 100 when supplied; use starting_after or ending_before to paginate the results.