Stripe product webhook events
Stripe sends 3 product events: product.created, product.deleted and product.updated.
Every event here can also reach agents as an MCP event through Hookdeck: MCP events →
product.created
documented official schema
product.created Product created
Identified by type field in the body
Resource product
stripe-product-created.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"active": true,
"created": 1234567890,
"default_price": "price_1PgafmB7WZ01zgkW02Hf9z6c",
"description": "Comfortable gray cotton t-shirt",
"id": "prod_QXg1hqf4jFNsqG",
"images": [ … ],
"livemode": false,
"marketing_features": [ … ],
"metadata": { … },
"name": "T-shirt",
"object": "product",
"type": "good"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "product.created"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | prod_QXg1hqf4jFNsqG |
data.object.type | string | good |
data.object.default_price | string | price_1PgafmB7WZ01zgkW02Hf9z6c |
data.object.created | integer | 1234567890 |
Full schema: 38 fields.
From Stripe docs
-
Content type
application/json
product.deleted
documented official schema
product.deleted Product deleted
Identified by type field in the body
Resource product
stripe-product-deleted.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"active": true,
"created": 1234567890,
"default_price": "price_1PgafmB7WZ01zgkW02Hf9z6c",
"description": "Comfortable gray cotton t-shirt",
"id": "prod_QXg1hqf4jFNsqG",
"images": [ … ],
"livemode": false,
"marketing_features": [ … ],
"metadata": { … },
"name": "T-shirt",
"object": "product",
"type": "good"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "product.deleted"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | prod_QXg1hqf4jFNsqG |
data.object.type | string | good |
data.object.default_price | string | price_1PgafmB7WZ01zgkW02Hf9z6c |
data.object.created | integer | 1234567890 |
Full schema: 38 fields.
From Stripe docs
-
Content type
application/json
product.updated
documented official schema
product.updated Product changes
Identified by type field in the body
Resource product
stripe-product-updated.json
{
"api_version": "2026-10-28.endive",
"created": 1234567890,
"data": {
"object": {
"active": true,
"created": 1234567890,
"default_price": "price_1PgafmB7WZ01zgkW02Hf9z6c",
"description": "Comfortable gray cotton t-shirt",
"id": "prod_QXg1hqf4jFNsqG",
"images": [ … ],
"livemode": false,
"marketing_features": [ … ],
"metadata": { … },
"name": "T-shirt",
"object": "product",
"type": "good"
}
},
"id": "evt_1Pgc76B7WZ01zgkWwyRHS12y",
"livemode": false,
"object": "event",
"pending_webhooks": 0,
"request": { … },
"type": "product.updated"
} Key fields
| Field | Type | Example |
|---|---|---|
data.object.id | string | prod_QXg1hqf4jFNsqG |
data.object.type | string | good |
data.object.default_price | string | price_1PgafmB7WZ01zgkW02Hf9z6c |
data.object.created | integer | 1234567890 |
Full schema: 38 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.