customer.updated
Fired when a customer's details change. Carries the full current customer resource.
Payload
All webhook payloads follow a consistent top-level structure with event-specific data nested within the data object.
The Commet customer ID (cus_...).
Your own identifier for this customer, if you provided one.
The customer's full name.
The customer's email.
The customer's timezone.
Custom key-value metadata you attached to the customer.
ISO 8601 datetime when the customer was created.
ISO 8601 datetime of this update.
{
"event": "customer.updated",
"timestamp": "2026-04-02T09:10:00.000Z",
"organizationId": "org_abc123",
"mode": "live",
"apiVersion": "2026-05-25",
"data": {
"id": "cus_1a2b3c4d",
"externalId": "user_123",
"fullName": "Ada Lovelace",
"email": "ada.lovelace@acme.com",
"timezone": "Europe/London",
"metadata": {
"plan_intent": "pro"
},
"createdAt": "2026-03-25T14:29:00.000Z",
"updatedAt": "2026-04-02T09:10:00.000Z"
}
}What counts as an update
The event fires when a customer field changes: email, fullName, timezone, externalId, or metadata. It carries the complete current resource, not a diff — replace your local copy with the payload.
Every distinct update delivers its own event, even several in quick succession. Like customer.created, the resource shape follows your endpoint's pinned API version.
How is this guide?