Skip to main content
PATCH
Bulk update accounts, contacts, or opportunities

Authorizations

x-api-key
string
header
required

Personal API key. Requests act as the workspace member who created the key, with that member's current access, and stop working when the key is disabled or its creator leaves the workspace.

Path Parameters

object_type
enum<string>
required

Object collection to update.

Available options:
accounts,
contacts,
opportunities

Body

application/json

Object keyed by target object UUID. Maximum 50 keys.

Bulk update payload keyed by object UUID. Accepted field names, read-API name → property_name. Accounts: name→company_name, domain→company_domain, industry→company_industry, description→company_description, founded→company_founded, linkedin→company_linkedin, twitter→company_twitter, twitter_followers→company_twitter_followers, primary_location→company_primary_location, estimated_revenue→company_estimated_revenue, total_fund_raised→company_total_fund_raised, employee_range→company_employee_range, type→company_type. Contacts: name→people_name (split into first and last name), first_name→people_first_name, last_name→people_last_name, account_id→people_account, job_title→people_job_title, seniority→people_seniority, linkedin→people_linkedin, twitter→people_twitter, phone→people_phone, current_company→people_current_company, other_emails→people_other_emails, type→people_type. Opportunities: name→opportunity_name, stage_id→opportunity_stage (moves the opportunity to that stage's pipeline; pipeline_id itself is not writable), amount→opportunity_deal_size (JSON number), probability→opportunity_probability (JSON number), close_date→opportunity_close_date and next_action_date→opportunity_next_action_date (ISO 8601 string or Unix timestamp in seconds or milliseconds), next_steps→opportunity_next_step, owner_id→opportunity_owner, account_id→opportunity_account, contact_id→opportunity_contact, additional_contacts→opportunity_other_stakeholders. Read-only and rejected with a message: ids, interaction timestamps, account logo and tags, and contact email, email_verified and avatar_url. For opportunities, relationship updates are expressed with system field names: opportunity_account for the associated account UUID, opportunity_contact for the primary contact UUID, and opportunity_other_stakeholders for the complete replacement list of additional contact UUIDs. These relationship fields replace the existing mapping for that field instead of appending.

{key}
object

Patch object. For opportunity relationship fields, pass UUID strings for opportunity_account and opportunity_contact, and an array of contact UUID strings for opportunity_other_stakeholders.

Response

Objects were updated.

success
boolean
Example:

true

message
string
data
any

Endpoint-specific response payload.