v3
Breaking Changes3
/crm/v3/objects/{objectType}/{objectId}
The deletion behavior for CRM objects has changed. Previously, deleting a contact or company would also delete associated records without confirmation. Now, deletion requires explicit confirmation, and associated records are not automatically deleted, preventing accidental data loss.
DELETE /crm/v1/objects/contacts/{contactId}DELETE /crm/v3/objects/contacts/{contactId}Update delete calls to include the confirmation query parameter if necessary and handle potential changes in associated record behavior.
/crm/v3/objects/contacts, /crm/v3/objects/companies
The endpoints for managing contacts and companies have been consolidated under the general CRM objects API. This restructuring simplifies the API surface but requires updating calls that previously used specific /contacts or /companies endpoints.
/contacts/v1/contact
/crm/v3/objects/contacts/{objectId}Migrate all calls from legacy contact and company endpoints to the new unified /crm/v3/objects/{objectType} endpoints.
id
The primary identifier field for all CRM objects is now consistently named 'id'. Previously, some objects might have used different naming conventions for their unique identifiers. This standardization ensures a predictable way to reference object IDs across the API.
Unique identifier field (e.g., 'contactId', 'companyId')
id
Update all references to object IDs to use the 'id' field name instead of older, object-specific names.
Never get blindsided by an API change again
Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.
Join the Waitlist