# WebhookFilingDigest

## Fields

Nested fields are written with dots; `[]` marks the items of an array.

| Field | Type | Always present | Description |
|---|---|---|---|
| `data` | object | yes | Its fields follow, as `data.…`. |
| `data.count` | integer | yes | — |
| `data.events` | array of object | yes | Each item's fields follow, as `data.events[].…`. |
| `data.events[].data` | object | no | — |
| `data.events[].type` | string | no | — |
| `data.truncated` | boolean | yes | — |
| `emitted_at` | date-time (RFC 3339, UTC) | yes | — |
| `id` | string | yes | Delivery ID, the same as the webhook-id header. It stays the same on every retry. |
| `schema_version` | integer | yes | One of: `1`. |
| `stream_seq` | integer | no | Position of a filing.\* event in the filing stream. |
| `subscription` | object \| null | no | The subscription that produced the event, as {id, name}. Null for a test send. Not present on endpoint.verification. |
| `subscription.id` | string | no | — |
| `subscription.name` | string | no | — |
| `test` | boolean | yes | True for a test send from POST /v3/callbacks/endpoints/{id}/test. Test sends carry sample data and are not billed. |
| `type` | string | yes | One of: `filing.digest`. |
