Skip to main content
objects

Create /objects

Create an object. Required: name and either contact (client UUID) or lead (lead UUID, when enabled for tenant). Optional: status (defaults to tenant default when omitted), serial number, active, contact person, contract, project, subdivision, responsible persons, types, address fields, dates, note, description, organization, and custom fields. Returns record with the detail projection.

POST
/objects
Authorizationstringheaderrequired

API key (Bearer token) created in Setup → API & MCP.

Body

application/json
activestring

Whether the object is active.

addressstring

Street address.

citystring

City.

contactstring

Client UUID (required on create if lead is omitted).

contact_personstring

Client contact person UUID.

contractstring

Contract UUID.

custom_fieldsobject[]

Custom field values by slug.

descriptionstring

Object description.

installation_datestring

Installation date (Y-m-d).

latitudestring

Latitude.

longitudestring

Longitude.

namestringrequired

Object name.

notestring

Internal note.

organizationstring

Organization UUID.

projectstring

Project UUID.

responsible_personstring[]

Responsible person staff UUIDs.

serial_nostring

Serial number.

statusstring

Object status UUID or code_name. Uses tenant default status when omitted on create.

subdivisionstring

Client subdivision UUID.

typestring[]

Object type UUIDs.

warranty_until_datestring

Warranty end date (Y-m-d).

Response

application/json

Success

recordobject

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.