Stripe reporting webhook events
Stripe sends 3 reporting events: reporting.report_run.failed, reporting.report_run.succeeded and reporting.report_type.updated.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
reporting.report_run.failed
documented official schema
reporting.report_run.failed Report run fails
Identified by type field in the body
Resource reporting
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"created": 1234567890,
"error": null,
"id": "frr_1Pgc79B7WZ01zgkWMmsefTsj",
"livemode": true,
"object": "reporting.report_run",
"parameters": { … },
"report_type": "balance.summary.1",
"result": { … },
"status": "succeeded",
"succeeded_at": 1234567890
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "reporting.report_run.failed"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | frr_1Pgc79B7WZ01zgkWMmsefTsj |
data.object.status | string | succeeded |
data.object.created | integer | 1234567890 |
Full schema: 34 fields.
From Stripe docs
-
Content type
application/json
reporting.report_run.succeeded
documented official schema
reporting.report_run.succeeded Report run completes
Identified by type field in the body
Resource reporting
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"created": 1234567890,
"error": null,
"id": "frr_1Pgc79B7WZ01zgkWMmsefTsj",
"livemode": true,
"object": "reporting.report_run",
"parameters": { … },
"report_type": "balance.summary.1",
"result": { … },
"status": "succeeded",
"succeeded_at": 1234567890
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "reporting.report_run.succeeded"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | frr_1Pgc79B7WZ01zgkWMmsefTsj |
data.object.status | string | succeeded |
data.object.created | integer | 1234567890 |
Full schema: 34 fields.
From Stripe docs
-
Content type
application/json
reporting.report_type.updated
documented official schema
reporting.report_type.updated Report type changes, typically when a new day's data is ready
Identified by type field in the body
Resource reporting
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"data_available_end": 1234567890,
"data_available_start": 1234567890,
"default_columns": [ … ],
"id": "balance.summary.1",
"livemode": true,
"name": "Balance summary",
"object": "reporting.report_type",
"updated": 1234567890,
"version": 1
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "reporting.report_type.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | balance.summary.1 |
Full schema: 22 fields.
From Stripe docs
-
Content type
application/json
Route Stripe events by type.
Event Gateway receives every Stripe delivery and filters and routes it by event type, so each service gets only the events it handles.