---
title: "Retrieve an event"
method: GET
path: "/v1/events/{id}"
---

# Retrieve an event

`GET /v1/events/{id}`

## Request

- Base URL: `https://api.stripe.com`
- URL: `https://api.stripe.com/v1/events/{id}`
- Auth: one of:
  - HTTP basic
  - HTTP bearer

Retrieves the details of an event if it was created in the last 30 days. Supply the unique identifier of the event, which you might have received in a webhook.

## Path parameters

- `id` string, required

## Query parameters

- `expand` string[]

## Response `200`

Successful response.

- Event: Snapshot events allow you to track and react to activity in your Stripe integration. When the state of another API resource changes, Stripe creates an `Event` object that contains all the relevant information associated with that action, including the affected API resource. For example, a successful payment triggers a `charge.succeeded` event, which contains the `Charge` in the event's data property. Some actions trigger multiple events. For example, if you create a new subscription for a customer, it triggers both a `customer.subscription.created` event and a `charge.succeeded` event. Configure an event destination in your account to listen for events that represent actions your integration needs to respond to. Additionally, you can retrieve an individual event or a list of events from the API. [Connect](https://docs.stripe.com/connect) platforms can also receive event notifications that occur in their connected accounts. These events include an account attribute that identifies the relevant connected account. You can access events through the [Retrieve Event API](https://docs.stripe.com/api/events#retrieve_event) for 30 days.
  - `account` string: The connected account that originates the event.
  - `api_version` string, nullable: The Stripe API version used to render `data` when the event was created. The contents of `data` never change, so this value remains static regardless of the API version currently in use. This property is populated only for events created on or after October 31, 2014.
  - `context` string: Authentication context needed to fetch the event or related object.
  - `created` integer, required: Time at which the object was created. Measured in seconds since the Unix epoch.
  - `data` NotificationEventData, required
    - `object` object, required: Object containing the API resource relevant to the event. For example, an `invoice.created` event will have a full [invoice object](https://docs.stripe.com/api#invoice_object) as the value of the object key.
    - `previous_attributes` object: Object containing the names of the updated attributes and their values prior to the event (only included in events of type `*.updated`). If an array attribute has any updated elements, this object contains the entire array. In Stripe API versions 2017-04-06 or earlier, an updated array attribute in this object includes only the updated array elements.
  - `id` string, required: Unique identifier for the object.
  - `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` 'event', required: String representing the object's type. Objects of the same type share the same value.
  - `pending_webhooks` integer, required: Number of webhooks that haven't been successfully delivered (for example, to return a 20x response) to the URLs you specify.
  - `request` NotificationEventRequest
    - `id` string, nullable: ID of the API request that caused the event. If null, the event was automatic (e.g., Stripe's automatic subscription handling). Request logs are available in the [dashboard](https://dashboard.stripe.com/logs), but currently not in the API.
    - `idempotency_key` string, nullable: The idempotency key transmitted during the request, if any. *Note: This property is populated only for events on or after May 23, 2017*.
  - `type` string, required: Description of the event (for example, `invoice.created` or `charge.refunded`).

## Other responses

- `default`: Error response.

## Changes

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

- **2026-07-01** `e24a26de4188`: 3 breaking
  - removed the required property `error/payment_intent/latest_charge/anyOf[subschema #2: Charge]/application_fee/anyOf[subschema #2: PlatformFee]/balance_transaction/anyOf[subschema #2: BalanceTransaction]/source/anyOf[subschema #6: Dispute]/payment_method_details/card/network` from the response with the `default` status
  - removed the required property `error/payment_intent/latest_charge/anyOf[subschema #2: Charge]/balance_transaction/anyOf[subschema #2: BalanceTransaction]/source/anyOf[subschema #6: Dispute]/payment_method_details/card/network` from the response with the `default` status
  - removed the required property `error/payment_intent/latest_charge/anyOf[subschema #2: Charge]/failure_balance_transaction/anyOf[subschema #2: BalanceTransaction]/source/anyOf[subschema #6: Dispute]/payment_method_details/card/network` from the response with the `default` status
  - …this revision’s changelog is incomplete

[Operation history](https://skmtc.dev/stainless-api/apis/stripe-api/changes/v1/events/:id/get.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)