Update a customer
Customers
Update Customer
PUT
Update a customer
Updates a customer’s information. All fields are optional — only send what you want to change.
Use
Authentication
Requires a valid Bearer token. The authenticated user must be a member of the organization.Path Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
organizationId | string (UUID) | Yes | Organization ID |
customerId | string | Yes | Customer ID |
Request Body
All fields are optional.| Field | Type | Description |
|---|---|---|
legalName | string | Legal name (Razón Social) |
taxId | string | RFC del receptor |
taxSystem | string | SAT tax system code |
email | string | Customer email |
phone | string | Phone number |
defaultInvoiceUse | string | Default CFDI use code |
addressStreet | string | Street name |
addressExterior | string | Exterior number |
addressInterior | string | Interior number |
addressNeighborhood | string | Neighborhood (Colonia) |
addressCity | string | City |
addressMunicipality | string | Municipality |
addressZip | string | 5-digit ZIP code |
addressState | string | State |
addressCountry | string | Country code |
Example Request
Example Response
Common Errors
400 Bad Request
Invalid field value (e.g. wrong RFC format or ZIP code).Fiscal validation error (CFDI 4.0)
WhentaxId, taxSystem, or defaultInvoiceUse are updated, the API re-validates the full taxId + taxSystem + defaultInvoiceUse combination against SAT CFDI 4.0 rules. RFC length determines persona type: 12 characters = persona moral, 13 characters = persona física. The régimen and uso CFDI must both be valid for that persona type, and the (uso, régimen) pair must exist in the SAT compatibility matrix.
GET /sat/regimenes-fiscales and GET /sat/usos-cfdi to look up valid codes and compatible combinations.
401 Unauthorized
Authentication required.403 Forbidden
User is not a member of this organization.404 Not Found
Customer not found.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
application/json
Customer legal name
Example:
"Dunder Mifflin"
Mexican RFC
Example:
"ABC101010111"
SAT tax system code
Example:
"601"
Customer email
Example:
"email@example.com"
Customer phone
Example:
"6474010101"
Default CFDI use code
Example:
"G01"
Street name
Exterior number
Interior number
Neighborhood
City
Municipality
ZIP code
State
Country code
Response
200 - application/json
Example:
"590ce6c56d04f840aa8438af"
Example:
"org-uuid"
Example:
"Dunder Mifflin"
Example:
"ABC101010111"
Example:
"601"
Example:
"email@example.com"
Example:
"G01"
Example:
"6474010101"