This endpoint can also be called using
PATCH /v1/customers/{customer_id} for REST-style updates.Request Body
ID of the customer to update.
Customer’s name. Pass
null to clear the value.Customer’s email address. Must be a valid email format. Pass
null to clear the value.Unique identifier (eg. serial number, device ID) to detect duplicate customers. Pass
null to clear the value.Additional metadata for the customer. Pass
null to clear all metadata, or provide an object to merge with existing metadata.Stripe customer ID. Use this to link the customer to an existing Stripe customer. Pass
null to clear the value.Whether to send email receipts to this customer.
New ID for the customer if you want to change their identifier. The new ID must follow the same validation rules as the original ID (no
@, spaces, or periods).Response
Returns the updated Customer object with the following fields:Your unique identifier for the customer (or the new ID if
new_customer_id was provided).The updated name of the customer.
The updated email address of the customer.
Timestamp of customer creation in milliseconds since epoch (unchanged).
The updated fingerprint identifier for the customer.
Updated Stripe customer ID.
The environment this customer was created in (
sandbox or live).The updated metadata for the customer.
Whether email receipts are enabled for this customer.
Active and scheduled recurring plans (unchanged by this operation).
One-time purchases (unchanged by this operation).
Feature balances (unchanged by this operation).
Example Requests
Example Response
Notes
- Only the fields you provide in the request will be updated. Other fields remain unchanged.
- To clear a nullable field, explicitly pass
nullas the value. - When updating metadata, the provided object is merged with existing metadata. To completely replace metadata, pass the complete new object.
- Changing the customer ID with
new_customer_idwill update the ID across all related records (subscriptions, balances, etc.).