Update customer by external ID
Update a customer by external ID. Changing externalId follows the organization-wide id rule: a new id that another customer already holds as its external id, a unit id or an alias, ignoring letter case, is refused with 409 EXTERNAL_ID_IN_USE; the same id in the same case stays 400 DUPLICATE_EXTERNAL_ID. When the id changes, the previous id is kept as an alias of the customer, so signals that still use it keep resolving to it.
Authentication
AuthorizationBearer
API Key authentication using Bearer token
Path parameters
externalId
Customer ID from the integrator’s system, stored on Paid as externalId.
Request
Body
name
legalName
email
phone
website
externalId
billingAddress
creationState
Allowed values:
churnDate
vatNumber
metadata
Response
200
id
Stable Paid customer display ID. Use this value as the {id} path parameter for customer routes, for example GET /api/v2/customers/cus_abc123/state.
name
legalName
email
phone
website
externalId
billingAddress
Customer billing address, or null when no address is set.
creationState
Allowed values:
status
Customer status: churned when the customer is marked as churned, active otherwise.
Allowed values:
churnDate
vatNumber
metadata
defaultCurrency
ISO 4217 currency code, for example USD, EUR, or GBP.
connections
Linked external system IDs for this customer.
createdAt
updatedAt
Errors
400
Bad Request Error
403
Forbidden Error
404
Not Found Error
409
Conflict Error
500
Internal Server Error