Create /clients
Create a client. Required: company. Optional: company code, VAT, contact details, address, legal type, types, categories, contact levels, responsible staff, organization. Returns record with the detail projection.
Side effect: unless the client already has one, a primary contact person is created alongside the client (same behaviour as creating a customer in the CRM UI). Its first/last name comes from company split on the first space, and it inherits phone and email. That contact is also returned by GET /contacts, so a 'New Contact' trigger fires for it.
Body
Contact level picklist value UUIDs (contacts/customer_level). Discover values via GET /api/v4/picklists. Pass [] to clear.
Response
Success
Fields enabled for this documentation instance (projection enabled: feature, option, subdomain, closures) plus account-level form field visibility. Role- and user-level field overrides are not applied here, so an API key whose staff user has such overrides may receive fewer fields. A disabled field is omitted from the response object entirely; a present key with a null value means the record simply has no value.
More in Clients
PATCHUpdate /clients/{uuid}DELDelete /clients/{uuid}Still need help? Ask the team