Upsert customer
PUT/v1/customers
Takes the same body as POST and dedups on id, public_id, external_id and document_number, in that order, stopping at the first key that finds a customer. A match is updated and returns 200; otherwise the customer is created and returns 201. Updates are partial: fields absent from the body keep their stored value.
Request​
Responses​
- 200
- 201
- 400
- 401
- 403
- 404
- 429
- 500
Customer updated.
Customer created.
Request body failed validation.
Missing or invalid bearer token.
Token is valid but lacks permission for this operation. With code insufficient_scope, details.required carries the one minimal set of scopes that, added to details.granted, would let the request through: the resource scope (billing/{resource}, or billing/all off the catalogue) then the bare verb — e.g. ["billing/customers", "delete"].
Resource not found in the current organization.
Rate limit exceeded.
Unexpected server error.