Sample HubSpot legacy API scan
When HubSpot ends support
Calls are grouped by the date HubSpot gives for their API, soonest first (HubSpot’s notices, checked on 2 October 2026).
4 Dec 2026 Pipelines API v1 (1)
HubSpot sunsets this API on 4 December 2026; its endpoints stop responding after that date (HubSpot’s notice). HubSpot’s legacy reference pages for it show 2 November 2026 instead; this report goes by the notice, the later one. The notice does not say whether the /deals/v1/pipelines calls of the older Deals API are part of it; they are v1 pipeline calls, so they are listed here too. Which of these calls the bridge translates.
| Where | Call | Bridge | Notes |
|---|---|---|---|
java/HubSpotLegacyClient.java:30 | GET /deals/v1/pipelines | Translated | GET /crm/pipelines/2026-09/deals |
30 Mar 2027 v4 APIs (1)
HubSpot ends support for its v4 APIs on 30 March 2027 (HubSpot’s notice).
| Where | Call | Bridge | Notes |
|---|---|---|---|
python/hubspot_client.py:30 | GET /automation/v4/flows | No date-based version yet | no date-based version of the automation workflows/flows API yet (v2/v3 workflows are succeeded by v4 flows, which has none either); served via the legacy endpoint; it lives as long as HubSpot keeps it (v2/v3 unsupported after September 2027, v4 from 30 March 2027) (passed through to the legacy endpoint while HubSpot keeps it: unsupported on 30 March 2027) |
Sep 2027 Other v1 to v3 APIs (33)
HubSpot says these APIs become unsupported after September 2027: no more bug fixes, reliability improvements or security updates. It has not announced a shutdown date for them (HubSpot’s notice).
| Where | Call | Bridge | Notes |
|---|---|---|---|
csharp/HubSpotDeals.cs:13 | POST /deals/v1/deal | Translated | POST /crm/objects/2026-09/deals |
csharp/HubSpotDeals.cs:16 | POST /crm/v3/associations/deals/{}/batch/read | Translated | POST /crm/associations/2026-09/{fromObjectType}/{toObjectType}/batch/read |
go/hubspot.go:13 | DELETE /contacts/v1/contact/vid/{} | Translated | DELETE /crm/objects/2026-09/contacts/{contactId} |
go/hubspot.go:30 | POST /crm-objects/v1/objects/tickets | Translated | POST /crm/objects/2026-09/tickets |
java/HubSpotLegacyClient.java:14 | GET /deals/v1/deal/{} | Translated | POST /crm/objects/2026-09/deals/batch/read |
java/HubSpotLegacyClient.java:22 | DELETE /companies/v2/companies/{} | Translated | DELETE /crm/objects/2026-09/companies/{companyId} |
node/sync-contacts.js:12 | POST /contacts/v1/contact/vid/{}/profile | Translated | PATCH /crm/objects/2026-09/contacts/{contactId} |
php/HubSpotLegacy.php:16 | PUT /deals/v1/deal/{} | Translated | PATCH /crm/objects/2026-09/deals/{dealId} |
python/hubspot_client.py:8 | GET /deals/v1/deal/paged | Translated | GET /crm/objects/2026-09/deals |
python/hubspot_client.py:13 | GET /crm-objects/v1/objects/tickets/{} | Translated | GET /crm/objects/2026-09/tickets/{ticketId} |
python/hubspot_client.py:22 | POST /crm/v3/objects/contacts/search | Translated | POST /crm/objects/2026-09/contacts/search |
ruby/hubspot.rb:14 | POST /contacts/v1/contact/createOrUpdate/email/{} | Translated | POST /crm/objects/2026-09/contacts/batch/upsert |
ts/base-urls.ts:12 | POST /contacts/v1/lists/{}/add | Translated | PUT /crm/lists/2026-09/{listId}/memberships/add |
ts/base-urls.ts:16 | POST /contacts/v1/lists/{}/remove | Translated | PUT /crm/lists/2026-09/{listId}/memberships/remove |
ts/base-urls.ts:21 | GET /contacts/v1/lists/static | Translated | POST /crm/lists/2026-09/search |
ts/modern.ts:5 | ? /crm/v3/objects/companies | Translated | GET /crm/objects/2026-09/companies |
ts/modern.ts:16 | POST /crm/v3/properties/{} | Translated | POST /crm/properties/2026-09/{objectType} |
ts/modern.ts:20 | PUT /crm/v3/objects/contacts/{}/associations/companies/{}/contact_to_company | Translated | PUT /crm/objects/2026-09/{objectType}/{objectId}/associations/{toObjectType}/{toObjectId} |
csharp/HubSpotDeals.cs:19 | GET /engagements/v1/engagements/associated/{}/{}/paged | Partly translated | merged from five association lists ordered by id; attachments are not carried |
go/hubspot.go:23 | GET /owners/v2/owners | Partly translated | only the HUBSPOT remote of each owner; remotes synced from other systems are not in the date-based API |
node/sync-contacts.js:7 | GET /contacts/v1/contact/vid/{}/profile | Partly translated | form-submissions, merge-audits and LEAD_GUID identities are not available in the date-based API; with property history, an answer over its version budget (50 000 hosted) keeps the newest versions |
node/sync-contacts.js:16 | GET /contacts/v1/lists/all/contacts/all | Partly translated | form-submissions, merge-audits and LEAD_GUID identities are not available in the date-based API; with property history, an answer over its version budget (50 000 hosted) keeps the newest versions |
node/sync-contacts.js:22 | POST /contacts/v1/contact/batch | Partly translated | auditId is not carried; a failed item no longer rejects the whole batch (reported as an error) |
php/HubSpotLegacy.php:10 | GET /companies/v2/companies/{} | Partly translated | includeMergeAudits is not carried |
php/HubSpotLegacy.php:24 | POST /engagements/v1/engagements | Partly translated | attachments and metadata keys without a date-based property are not carried |
python/hubspot_client.py:18 | PUT /crm-associations/v1/associations | Partly translated | engagement definitions (7-12, 17, 18) have no date-based equivalent |
ruby/hubspot.rb:9 | GET /contacts/v1/contact/email/{}/profile | Partly translated | form-submissions, merge-audits and LEAD_GUID identities are not available in the date-based API; with property history, an answer over its version budget (50 000 hosted) keeps the newest versions |
ts/base-urls.ts:20 | GET /contacts/v1/contact/vid/{}/profile | Partly translated | form-submissions, merge-audits and LEAD_GUID identities are not available in the date-based API; with property history, an answer over its version budget (50 000 hosted) keeps the newest versions |
python/hubspot_client.py:26 | GET /forms/v2/forms | No date-based version yet | no date-based Forms API yet (2027-03-beta only); served via /marketing/v3/forms, whose FormDefinitionBase schema the beta keeps (translated to this legacy API until HubSpot ships a date-based version) |
ruby/hubspot.rb:21 | GET /automation/v3/workflows | No date-based version yet | no date-based version of the automation workflows/flows API yet (v2/v3 workflows are succeeded by v4 flows, which has none either); served via the legacy endpoint; it lives as long as HubSpot keeps it (v2/v3 unsupported after September 2027, v4 from 30 March 2027) (passed through to the legacy endpoint while HubSpot keeps it: unsupported after September 2027) |
ts/base-urls.ts:22 | POST /forms/v2/forms | No date-based version yet | no date-based Forms API yet (2027-03-beta only); written via /marketing/v3/forms: v2-only settings (follow-up, lead nurturing, theme name, non-default groups, page breaks, disabled or smart fields, blocked e-mail addresses) are not carried (translated to this legacy API until HubSpot ships a date-based version) |
php/HubSpotLegacy.php:31 | PUT /integrations/v1/{}/timeline/event | Not translated | legacy v1 endpoint without a mapped date-based counterpart; not translated yet |
ts/modern.ts:24 | POST /crm/v3/timeline/events | Unknown legacy path |
Credentials
- 4 places use
hapikey(API keys, retired by HubSpot) — the bridge accepts?hapikey=<bridge key>. - 1 legacy private app tokens (
pat-…) in code — replace them with the bridge key (and rotate them).