Update account
Updates an account by its id and returns the updated record. Responds 404 if no account with that id exists in the authenticated company. Setting externalId here is how accounts that predate your integration get their id; a value already on another live account is a 409.
Authorization
AuthorizationRequiredBearer <token>API key as Bearer token: Authorization: Bearer sk_live_.... Use sk_live_ prefixed keys for production data and sk_test_ prefixed keys for sandbox/test data.
In: header
X-API-Key<token>API key via header: X-API-Key: sk_live_.... Use sk_live_ prefixed keys for production data and sk_test_ prefixed keys for sandbox/test data.
In: header
Request Body
application/jsonRequiredexternalIdstringYour own id for the organisation — a customer or tenant id from your system. Send it on every create and the endpoint becomes find-or-create: if a live account in this workspace already carries this id, that account is returned with 200 and nothing is created or changed. Otherwise the account is created with 201.
Name is never used for matching. Two organisations with the same name and different ids are two accounts, on purpose — matching on name would attach one customer's signup to another customer's record. Omit the field and the endpoint always creates.
namestringwebsitestringindustrystringsizestring"small" | "medium" | "large" | "enterprise"phonestringaddressstringextraInformationstringstatusstring"active"Value in: "active" | "inactive" | "prospect" | "customer" | "churned"tagsarray<string>Path Parameters
idRequiredstringResource ID
"uuid"Updated account