Sample HubSpot legacy API scan

Demo data: a fictional code base. Upload your own code to see yours.
The bridge translates
82.9%
of 35 legacy calls found
By status
translated 19
partial 10
unsupported 2
no date-based version yet: 4 (bridged: translated 2, passed through 2)
Scanned
9
code files from the archive

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.

WhereCallBridgeNotes
java/HubSpotLegacyClient.java:30GET /deals/v1/pipelinesTranslatedGET /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).

WhereCallBridgeNotes
python/hubspot_client.py:30GET /automation/v4/flowsNo date-based version yetno 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).

WhereCallBridgeNotes
csharp/HubSpotDeals.cs:13POST /deals/v1/dealTranslatedPOST /crm/objects/2026-09/deals
csharp/HubSpotDeals.cs:16POST /crm/v3/associations/deals/{}/batch/readTranslatedPOST /crm/associations/2026-09/{fromObjectType}/{toObjectType}/batch/read
go/hubspot.go:13DELETE /contacts/v1/contact/vid/{}TranslatedDELETE /crm/objects/2026-09/contacts/{contactId}
go/hubspot.go:30POST /crm-objects/v1/objects/ticketsTranslatedPOST /crm/objects/2026-09/tickets
java/HubSpotLegacyClient.java:14GET /deals/v1/deal/{}TranslatedPOST /crm/objects/2026-09/deals/batch/read
java/HubSpotLegacyClient.java:22DELETE /companies/v2/companies/{}TranslatedDELETE /crm/objects/2026-09/companies/{companyId}
node/sync-contacts.js:12POST /contacts/v1/contact/vid/{}/profileTranslatedPATCH /crm/objects/2026-09/contacts/{contactId}
php/HubSpotLegacy.php:16PUT /deals/v1/deal/{}TranslatedPATCH /crm/objects/2026-09/deals/{dealId}
python/hubspot_client.py:8GET /deals/v1/deal/pagedTranslatedGET /crm/objects/2026-09/deals
python/hubspot_client.py:13GET /crm-objects/v1/objects/tickets/{}TranslatedGET /crm/objects/2026-09/tickets/{ticketId}
python/hubspot_client.py:22POST /crm/v3/objects/contacts/searchTranslatedPOST /crm/objects/2026-09/contacts/search
ruby/hubspot.rb:14POST /contacts/v1/contact/createOrUpdate/email/{}TranslatedPOST /crm/objects/2026-09/contacts/batch/upsert
ts/base-urls.ts:12POST /contacts/v1/lists/{}/addTranslatedPUT /crm/lists/2026-09/{listId}/memberships/add
ts/base-urls.ts:16POST /contacts/v1/lists/{}/removeTranslatedPUT /crm/lists/2026-09/{listId}/memberships/remove
ts/base-urls.ts:21GET /contacts/v1/lists/staticTranslatedPOST /crm/lists/2026-09/search
ts/modern.ts:5? /crm/v3/objects/companiesTranslatedGET /crm/objects/2026-09/companies
ts/modern.ts:16POST /crm/v3/properties/{}TranslatedPOST /crm/properties/2026-09/{objectType}
ts/modern.ts:20PUT /crm/v3/objects/contacts/{}/associations/companies/{}/contact_to_companyTranslatedPUT /crm/objects/2026-09/{objectType}/{objectId}/associations/{toObjectType}/{toObjectId}
csharp/HubSpotDeals.cs:19GET /engagements/v1/engagements/associated/{}/{}/pagedPartly translatedmerged from five association lists ordered by id; attachments are not carried
go/hubspot.go:23GET /owners/v2/ownersPartly translatedonly the HUBSPOT remote of each owner; remotes synced from other systems are not in the date-based API
node/sync-contacts.js:7GET /contacts/v1/contact/vid/{}/profilePartly translatedform-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:16GET /contacts/v1/lists/all/contacts/allPartly translatedform-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:22POST /contacts/v1/contact/batchPartly translatedauditId is not carried; a failed item no longer rejects the whole batch (reported as an error)
php/HubSpotLegacy.php:10GET /companies/v2/companies/{}Partly translatedincludeMergeAudits is not carried
php/HubSpotLegacy.php:24POST /engagements/v1/engagementsPartly translatedattachments and metadata keys without a date-based property are not carried
python/hubspot_client.py:18PUT /crm-associations/v1/associationsPartly translatedengagement definitions (7-12, 17, 18) have no date-based equivalent
ruby/hubspot.rb:9GET /contacts/v1/contact/email/{}/profilePartly translatedform-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:20GET /contacts/v1/contact/vid/{}/profilePartly translatedform-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:26GET /forms/v2/formsNo date-based version yetno 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:21GET /automation/v3/workflowsNo date-based version yetno 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:22POST /forms/v2/formsNo date-based version yetno 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:31PUT /integrations/v1/{}/timeline/eventNot translatedlegacy v1 endpoint without a mapped date-based counterpart; not translated yet
ts/modern.ts:24POST /crm/v3/timeline/eventsUnknown 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).

Next step

See pricingConnection guideScan your own code