HubSpot: CRM
- Contacts API v3
- Companies API v3
- Deals API v3
- Tickets API v3
- Properties API v3
- Pipelines API v3
- Lists API v3
- Owners API v3
- Associations API v4
Vendor coverage
HubSpot API changes & breaking changes
CRM integrations outlive the people who wrote them: contacts, companies, and deals syncing into billing, support, and data warehouses. Detektu diffs HubSpot's published CRM contracts so an object schema change becomes a finding before it becomes a broken sync.
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How HubSpot ships changes
The release patterns that shape your integration risk.
HubSpot publishes OpenAPI contracts for its CRM APIs: core objects, properties, pipelines, lists, owners, and the v4 associations model. The surface evolves steadily, and sync code written against v3 objects tends to run unattended for years.
Detektu watches each contract separately and names the exact object API and property that changed, so you can match findings against the objects your sync actually reads and writes.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Response field removed from the contacts object
openapi:GET /crm/v3/objects/contacts/{contactId} ::response.200.propertiesNew batch operation on the associations v4 API
openapi:POST /crm/v4/associations/{fromObjectType}/{toObjectType}/batch/createMonitored for you
Do HubSpot's changes affect your integration?
Choose the operations and fields your services use. Detektu matches HubSpot findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.