Skip to content

Legacy private apps and legacy public apps become unsupported in September 2027; existing private-app tokens keep working until then.

Documented

Area

Tags

private-apps, public-apps, legacy, unsupported

Sources

developers.hubspot.com/changelog/legacy-apis-and-legacy-apps-whats-going-unsupported-and-when

More facts from this area

hs api <endpoint> --account=<id> --json authenticates with the CLI's personal access key, which reaches portals that have no pat- token, including the legacy /content/api/v2/* endpoints.Measured
A public OAuth app can't read object tags: GET /crm/object-tags/{v}/0-3 returns 403 "The scope needed for this API call isn't available for public use".Measured
The CLI's personal access key isn't usable as a bearer token (401 EXPIRED_AUTHENTICATION); only pat- private-app tokens are.Measured
Creating legacy private apps is disabled for new accounts from September 28, 2026 and for existing accounts from October 26, 2026; service keys replace them.Documented
A private-app (pat-) token is rejected by the OAuth introspection endpoint GET /oauth/v1/access-tokens/{token}; read the portal from GET /account-info/v3/details instead.Measured

Spriggit uses these facts when it plans changes. See something out of date? Email [email protected]