Users

Contact people are managed below the contact and address they belong to. The nested URL prevents a user from being accidentally addressed outside its parent records.

User context

Nested operations use contacts:read or contacts:write. The global query endpoints use users:read. Route parameters accept IDs or identifiers and enforce parent-child ownership.

QUERY/api/v1/users

Query users

Searches users with the current HTTP QUERY model, including supported options such as licensed-only filtering. Required scope: users:read.

POST/api/v1/users/query

Structured user query

Runs a JSON query against user resources. Required scope: users:read.

GET/api/v1/contacts/{contact}/addresses/{address}/users

List address users

Lists contact people assigned to the address.

POST/api/v1/contacts/{contact}/addresses/{address}/users

Create an address user

Creates a contact person in the nested address context.

GET/api/v1/contacts/{contact}/addresses/{address}/users/{user}

Get an address user

Returns one nested contact person.

PATCH/api/v1/contacts/{contact}/addresses/{address}/users/{user}

Update an address user

Updates one contact person. PUT is also registered.

DELETE/api/v1/contacts/{contact}/addresses/{address}/users/{user}

Delete an address user

Soft-deletes the contact person.

POST/api/v1/contacts/{contact}/addresses/{address}/users/{user}/restore

Restore an address user

Restores the soft-deleted user and revalidates the complete parent path.

POST/api/v1/users/{userId}/restore

Restore a user by ID

Restores a soft-deleted user using its record ID. Required scope: users:write.

Was this page helpful?