HubSpot is retiring v1–v4 APIs and private apps. Is our stack ready for 2027?

Two clocks are running. Anything calling a v4 endpoint has until March 30, 2027. Anything on v1–v3 is already unsupported, with enforcement in September 2027, which is also the deadline for moving legacy private apps to service keys. This skill inventories your portal’s API surface and flags everything on a legacy version or a legacy app, with a migration checklist.

The deadline fails quietly: unsupported APIs "no longer receive updates, bug fixes, or stability guarantees," and marketplace apps that don't migrate risk losing certification. A portal typically has more callers than anyone remembers — service keys, legacy private apps, marketplace apps, middleware (Zapier/Make), form embeds, internal scripts, data warehouse syncs. Finding them takes an afternoon now or an incident later. — from the Audit API Usage Before the 2027 Cutoffs skill

Fix it with one command

The audit-api-usage skill walks Claude Code through the entire fix — audit, CSV baseline, execution, and verification.

/plugin marketplace add tomgranot/hubspot-admin-skills
/plugin install hubspot-admin@hubspot-admin-skills
/audit-api-usage

Frequently asked questions

Can I still create a HubSpot private app?

Not after October 26, 2026. Accounts created on or after September 28, 2026 never had the option. Existing private apps keep working and must migrate by September 2027. New internal integrations use a service key, created under Settings > Integrations > Service Keys.

What replaced HubSpot’s v3 and v4 API versions?

Date-based versions (currently 2026-09), released every March and September with at least 18 months of support each. v4 endpoints are supported until March 30, 2027. v1–v3 have been unsupported since September 2026 and are enforced from September 2027.

More audit & planning skills