HubSpot 13.0.0 breaking change: cms.blogs.blogPostsApi methods moved to basicApi/batchApi/multiLanguageApi
What changed
From the upstream announcement:
CMS Moved methods archive , callClone , create , getById , pushLive , resetDraft , schedule , update and updateDraft from cms.blogs.blogPostsApi to cms.blogs.basicApi . Moved and renamed methods archiveBatch => archive , createBatch => create , readBatch => read and updateBatch => update from cms.blogs.blogPostsApi to cms.blogs.batchApi . Moved methods attachToLangGroup , createLangVariation , detachFromLangGroup , setLangPrimary and updateLangs from cms.blogs.blogPostsApi to cms.blogs.multiLanguageApi . Events Renamed events.send.customEventDataApi to events.send.basicApi . Added events.send.batchApi API. Files Renamed method archiveGDPR() to _delete() in files.filesApi . Changed incomining parameters list in files.filesApi.doSearch . Changed incomining parameters list in files.foldersApi.doSearch . Renamed method updateProperties() to updatePropertiesRecursively() in files. […]
Who is affected
Codebases that call the HubSpot API surface named above.
To find out whether your repo is hit — file and line number, no code leaving your machine:
npx mendapi sync # the one network call: fetch the change feed npx mendapi scan --repo . # local scan, nothing leaves your machine
How to fix it
mendapi ships a deterministic migration pack for this change (hubspot-blogposts-api-move). Preview the patch locally (dry-run is the default; nothing is modified without --apply):
npx mendapi fix --repo . --migration hubspot-blogposts-api-move
The pack is idempotent, gold-regression tested, and safe on partially migrated code.
Detected and tracked by mendapi — Dependabot for every API you depend on. Scans run locally; your code never leaves your machine.
Related
- hubspot breaking-change guide — every tracked hubspot entry on one page, with fixability verdicts.
- All monitored providers — live change counts for hubspot and 19 others.
- Migration pack catalog — every deterministic fix mendapi ships.
- Getting started — scan your repo in 30 seconds, no code leaves your machine.
Change data is recorded from upstream provider releases, changelogs and OpenAPI spec diffs; every article names its source.