# The Engagements API v1 is deprecated

HubSpot API deprecated /engagements/v1/* without giving a shutdown date yet.

On September 15, 2026, HubSpot deprecated the /engagements/v1/* endpoints without announcing a shutdown date. Calls to these routes will eventually fail, as numbered version paths will move to unsupported status without future bug fixes, reliability improvements, or security updates.

## What to use instead

Move to the activity object APIs on date-based versioning at /crm/objects/2026-09/{notes|calls|emails|meetings|tasks}. Because HubSpot has not finalized every legacy endpoint's date-based replacement yet, some alternatives will be documented in its March 2027 release.

HubSpot has not finalized every legacy endpoint's date-based replacement yet; it documents them in its March 2027 release.

- API: HubSpot API (api.hubapi.com)
- Kind: Version retirement
- Announced: September 15, 2026
- Takes effect: no date given yet
- Calls after that day: fail
- Calls it hits: `/engagements/v1/*`
- Source: [Announcement](https://developers.hubspot.com/changelog/legacy-apis-and-legacy-apps-whats-going-unsupported-and-when)
- Verified: November 6, 2026, against HubSpot API's own pages
- Page: https://www.okapi.bot/providers/hubspot-api/breaking-changes/the-engagements-api-v1-is-deprecated/

## HubSpot API's words

> Endpoints using numbered version paths, /v1/ , /v2/ , and /v3/ , will move to unsupported status. HubSpot will no longer release bug fixes, reliability improvements, or security updates for these versions.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent