How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Stripe Billing Meters API

Meters specify how to aggregate meter events over a billing period for usage-based pricing. Meter events represent customer actions and support up to 10,000 events per second via the V2 meter event streams API.

Stripe Billing Meters API is one of 159 APIs that Stripe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Billing, Meters, and Usage-Based. The published artifact set on APIs.io includes an API reference, API documentation, and an OpenAPI specification.

This API exposes 8 operations across 6 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2023-10-16.

Requests are made against a single base URL, https://api.stripe.com/.

8 operations 6 paths 4 schemas 3 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2023-10-16
Server
https://api.stripe.com/
Authentication
HTTP Basic, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Stripe Billing Meters API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). It accepts HTTP bearer tokens (auth-scheme) (bearerAuth). By default, every request must be authenticated.

  • basicAuth — Basic HTTP authentication. Allowed headers-- Authorization: Basic | Authorization: Basic
  • bearerAuth — Bearer HTTP authentication. Allowed headers-- Authorization: Bearer

Paths & Operations 8

Across 6 paths, the API surfaces 8 operations — 3 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Billing Meters 8
GET
/v1/billing/meters
Stripe List Billing Meters
GetBillingMeters 4 params → 200default
POST
/v1/billing/meters
Stripe Create Billing Meter
PostBillingMeters body → 200default
GET
/v1/billing/meters/{id}
Stripe Retrieve Billing Meter
GetBillingMetersId 1 param → 200default
POST
/v1/billing/meters/{id}
Stripe Update Billing Meter
PostBillingMetersId 1 param body → 200default
POST
/v1/billing/meters/{id}/deactivate
Stripe Deactivate Billing Meter
PostBillingMetersIdDeactivate 1 param → 200default
POST
/v1/billing/meters/{id}/reactivate
Stripe Reactivate Billing Meter
PostBillingMetersIdReactivate 1 param → 200default
GET
/v1/billing/meters/{id}/event_summaries
Stripe List Meter Event Summaries
GetBillingMetersIdEventSummaries 8 params → 200default
POST
/v1/billing/meter_events
Stripe Create Meter Event
PostBillingMeterEvents body → 200default

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are billing.meter (13 properties), billing.meter_event_summary (7 properties), billing.meter_event (7 properties), error (1 property). Each schema is shown below with its type and property counts.

billing.meter_event
object
7 properties 6 required
billing.meter_event_summary
object
7 properties 7 required
billing.meter
object
13 properties 11 required
error
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

stripe-billing-meters-api-openapi.yml Raw ↑

Other APIs Stripe publishes across the network.

Stripe Accounts API
Stripe Balance API
Stripe Billing API
Stripe Charges API
Stripe Checkout API
Stripe Climate API
Stripe Country API
Stripe Coupons API
Stripe Credit Notes API
Stripe Customers API
Stripe Disputes API
Stripe Ephemeral Keys API
Where this information came from

This is an independent, third-party profile of Stripe Billing Meters API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.