---
title: "Create a billing meter event adjustment"
method: POST
path: "/v1/billing/meter_event_adjustments"
---

# Create a billing meter event adjustment

`POST /v1/billing/meter_event_adjustments`

## Request

- Base URL: `https://api.stripe.com`
- URL: `https://api.stripe.com/v1/billing/meter_event_adjustments`
- Auth: one of:
  - HTTP basic
  - HTTP bearer

Creates a billing meter event adjustment.

## Response `200`

Successful response.

- BillingMeterEventAdjustment: A billing meter event adjustment is a resource that allows you to cancel a meter event. For example, you might create a billing meter event adjustment to cancel a meter event that was created in error or attached to the wrong customer.
  - `cancel` BillingMeterResourceBillingMeterEventAdjustmentCancel
    - `identifier` string, nullable: Unique identifier for the event.
  - `event_name` string, required: The name of the meter event. Corresponds with the `event_name` field on a meter.
  - `livemode` boolean, required: If the object exists in live mode, the value is `true`. If the object exists in test mode, the value is `false`.
  - `object` 'billing.meter_event_adjustment', required: String representing the object's type. Objects of the same type share the same value.
  - `status` 'complete' | 'pending', required: The meter event adjustment's status.
  - `type` 'cancel', required: Specifies whether to cancel a single event or a range of events for a time period. Time period cancellation is not supported yet.

## Other responses

- `default`: Error response.

## Changes

> 19 revisions in range; 7 not diffed, 2 could not be searched.

- **2026-09-25** `8b5c2f03d4cd`: 11 info
  - added the optional property `error/payment_intent/latest_charge/anyOf[subschema #2: Charge]/payment_method_details/anyOf[subschema #1: payment_method_details]/bancontact/generated_sepa_debit_mandate/anyOf[subschema #2: Mandate]/payment_method_details/card/india` to the response with the `default` status
  - added the optional property `error/payment_intent/latest_charge/anyOf[subschema #2: Charge]/payment_method_details/anyOf[subschema #1: payment_method_details]/card/mandate/anyOf[subschema #2: Mandate]/payment_method_details/card/india` to the response with the `default` status
  - added the optional property `error/payment_intent/latest_charge/anyOf[subschema #2: Charge]/payment_method_details/anyOf[subschema #1: payment_method_details]/ideal/generated_sepa_debit_mandate/anyOf[subschema #2: Mandate]/payment_method_details/card/india` to the response with the `default` status
  - added the optional property `error/payment_intent/latest_charge/anyOf[subschema #2: Charge]/payment_method_details/anyOf[subschema #1: payment_method_details]/sofort/generated_sepa_debit_mandate/anyOf[subschema #2: Mandate]/payment_method_details/card/india` to the response with the `default` status
  - …7 more
  - …this revision’s changelog is incomplete
- …earlier changes not shown

[Operation history](https://skmtc.dev/stainless-api/apis/stripe-api/changes/v1/billing/meter_event_adjustments/post.md)

---

[API](https://skmtc.dev/stainless-api/apis/stripe-api.md) · [All operations](https://skmtc.dev/stainless-api/apis/stripe-api/llms.txt) · [OpenAPI document](https://skmtc.dev/stainless-api/apis/stripe-api/revisions/7cff4cc46d06?raw)