Contacts

Contacts are organizations or customers and are the parent of addresses, address users, projects, devices, and contracts.

Identifiers and provider fields

Resource paths accept a record ID or the record's external identifier. External identifiers are opaque strings assigned by the source system. Provider-specific fields use the custom-field group configured through Custom Fields & Mappings.

Use JSON Schemas to retrieve the current request fields and validation constraints instead of relying on a frozen field list in a client.

GET/api/v1/contacts

List contacts

Required scope: contacts:read. Supports shared collection filtering, relation loading, limit, and opt-in perPage pagination.

POST/api/v1/contacts/query

Query contacts

Required scope: contacts:read. Send a structured JSON query with POST to /contacts/query.

POST/api/v1/contacts

Create a contact

Required scope: contacts:write. Send fields accepted by the current contact.schema.json, including a stable external identifier when synchronizing another system.

GET/api/v1/contacts/{contact}

Get a contact

Required scope: contacts:read. {contact} accepts ID or identifier.

PATCH/api/v1/contacts/{contact}

Update a contact

Required scope: contacts:write. PUT is also registered.

DELETE/api/v1/contacts/{contact}

Delete a contact

Required scope: contacts:write. Returns 204 No Content on success.

POST/api/v1/contacts/{contact}/restore

Restore a contact

Restores a soft-deleted contact. Required scope: contacts:write.

Was this page helpful?