> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mycryptoserver.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events

> Log of all events delivered to your webhook endpoints

Every event that My Crypto Server fires — whether delivered successfully or not — is recorded and accessible through the Events API. You can use this to audit deliveries, replay missed events, or reconcile your system.

## The event object

| Field       | Type     | Description                                                    |
| ----------- | -------- | -------------------------------------------------------------- |
| `id`        | uuid     | Unique identifier                                              |
| `object`    | string   | Always `"event"`                                               |
| `type`      | string   | Event type, e.g. `session.paid`                                |
| `livemode`  | boolean  | `true` for live transactions, `false` for test                 |
| `data`      | object   | The resource that triggered the event (e.g. a CheckoutSession) |
| `createdAt` | datetime |                                                                |

## Event types

| Type                | Triggered when                                          |
| ------------------- | ------------------------------------------------------- |
| `session.paid`      | Payment confirmed with required confirmations           |
| `session.paid_late` | Payment confirmed after expiry, within the grace window |
| `session.expired`   | Session timed out with no payment                       |
| `session.detected`  | Transfer first detected on-chain                        |
| `session.underpaid` | Transfer detected but amount is insufficient            |
| `session.overpaid`  | Transfer detected but amount exceeds what was expected  |

<Note>
  Events require `events:read` scope.
</Note>

<api-reference openapi="GET /events" />

<api-reference openapi="GET /events/{id}" />