Stripe plan webhook events
Stripe sends 3 plan events: plan.created, plan.deleted and plan.updated.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
plan.created
documented official schema
plan.created Plan created
Identified by type field in the body
Resource plan
stripe-plan-created.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"active": true,
"amount": 2000,
"amount_decimal": "2000",
"billing_scheme": "per_unit",
"created": 1234567890,
"currency": "usd",
"id": "price_1PgafmB7WZ01zgkW6dKueIc5",
"interval": "month",
"interval_count": 1,
"livemode": false,
"metadata": { … }
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "plan.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | price_1PgafmB7WZ01zgkW6dKueIc5 |
data.object.amount | integer | 2000 |
data.object.created | integer | 1234567890 |
Full schema: 33 fields.
From Stripe docs
-
Content type
application/json
plan.deleted
documented official schema
plan.deleted Plan deleted
Identified by type field in the body
Resource plan
stripe-plan-deleted.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"active": true,
"amount": 2000,
"amount_decimal": "2000",
"billing_scheme": "per_unit",
"created": 1234567890,
"currency": "usd",
"id": "price_1PgafmB7WZ01zgkW6dKueIc5",
"interval": "month",
"interval_count": 1,
"livemode": false,
"metadata": { … }
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "plan.deleted"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | price_1PgafmB7WZ01zgkW6dKueIc5 |
data.object.amount | integer | 2000 |
data.object.created | integer | 1234567890 |
Full schema: 33 fields.
From Stripe docs
-
Content type
application/json
plan.updated
documented official schema
plan.updated Plan changes
Identified by type field in the body
Resource plan
stripe-plan-updated.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"active": true,
"amount": 2000,
"amount_decimal": "2000",
"billing_scheme": "per_unit",
"created": 1234567890,
"currency": "usd",
"id": "price_1PgafmB7WZ01zgkW6dKueIc5",
"interval": "month",
"interval_count": 1,
"livemode": false,
"metadata": { … }
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "plan.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | price_1PgafmB7WZ01zgkW6dKueIc5 |
data.object.amount | integer | 2000 |
data.object.created | integer | 1234567890 |
Full schema: 33 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.