Full update of a resource
Authorizations
Enter your API key with the Bearer prefix — e.g. Bearer sk_live_xxx (production) or Bearer sk_test_xxx (sandbox)
Headers
Identifier of the end user whose connected provider should be queried. This is the same endUserId you supplied when creating the connect token. Required on every CRM and accounting call.
"user-001"
Path Parameters
Canonical CRM resource type to update. Must be one of the values in the enum below. RouteMCP maps this to the equivalent provider-native object (e.g. contact → HubSpot Contacts, Pipedrive Persons, Zoho Contacts). owner and pipeline are read-only and cannot be updated.
contact, lead, deal, meeting, company, note, task, activity, appointment Provider-native record id. This is the id as it appears in the source system (e.g. a HubSpot contact id, a Pipedrive deal id, a QuickBooks invoice id). Use the remote_id field returned by the list endpoint.
"12345"
Query Parameters
Provider slug identifying which connected provider to target (e.g. hubspot, pipedrive, zoho-crm, quickbooks-online, xero, zoho-books). Required — single-record operations always target a specific provider.
"hubspot"
Body
Full replacement body (PUT). Sends the complete record — fields not supplied are reset to their defaults or cleared, depending on the provider. Same required fields as create.
- Contact
- Lead
- Deal
- Meeting
- Company
- Note
- Task
- Activity
- Appointment
Given name of the contact.
"Gil"
Family name of the contact.
"Feig"
Provider-native ID of the associated account (company). Format is provider-specific.
"420578000000250001"
Provider-native ID of the record owner.
"420578000000250001"
Postal addresses for this contact. Most providers persist only the first (primary) address.
Email addresses for this contact. The first entry is treated as the primary email.
Phone numbers for this contact. The first entry is treated as the primary phone.
Response
Resource fully updated
Standard envelope returned by PUT /crm/{resource}/{id} and PATCH /crm/{resource}/{id}. Contains the record as it exists after the write. The shape of data depends on the {resource} path parameter — see the tabs to switch between resource variants.
Always true for successful (2xx) responses.
true
HTTP status code mirrored inside the envelope.
200
"OK"
A person record (typically associated with a company/account).
- Contact
- Lead
- Deal
- Meeting
- Company
- Note
- Task
- Activity
- Appointment