Skip to content

Bulk Update Contacts

POST
/contacts/bulk-update

Apply a DIFFERENT change to each of many contacts.

The whole target set is authorised before the first write, so a batch containing one contact the key cannot write is refused outright rather than half-applied.

After that preflight, individual failures are REPORTED, not fatal: read updated, failed and the per-contact errors rather than the HTTP status.

Authorizations

Parameters

Header Parameters

X-Target-Org-Id
Any of:
string

Request Body required

One object per contact. Each MUST carry id; every other key is a field to set on that contact.

Array<object>
object
key
additional properties
any

Responses

200

Successful Response

object
data
required

An open envelope for one record, one dashboard or one job receipt.

Open because most of these reads are COMPUTED shapes - an engagement summary, a next-best-step, an intelligence status - that grow with the product, and dropping a field from an advisory read makes it say “nothing to report” rather than “we did not tell you”.

object
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
notes
Any of:
Array<string>
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer
total_available
Any of:
integer
total_is_lower_bound
Any of:
boolean

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string