# V1 OAuth API Deprecation

**URL:** <https://community.hubspot.com/t/v1-oauth-api-deprecation/149267>\
**Category:** Developer Announcements\
**Tags:** api, announcement\
**Created:** [May 12, 2026, 12:56pm UTC](https://community.hubspot.com/t/v1-oauth-api-deprecation/149267 "2026-05-12T12:56:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hseligson](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hseligson/32/20940_2.png) [@hseligson](https://community.hubspot.com/u/hseligson)\
**Post date:** [May 12, 2026, 12:56pm UTC](https://community.hubspot.com/t/v1-oauth-api-deprecation/149267/1 "2026-05-12T12:56:52Z")

</div>

We have introduced the [latest date-based, versioned OAuth AP](https://developers.hubspot.com/docs/api-reference/latest/authentication/manage-oauth-tokens)I for token issuance and introspection, as announced previously[here](https://developers.hubspot.com/changelog/new-oauth-v3-api-endpoints-and-standardized-error-responses). As adoption of the new OAuth API grows, we are beginning to deprecate the legacy v1 OAuth API. As part of this transition, **a new REVOKE endpoint is also being introduced for the latest date-based versioned OAuth API,** and **the v1 API will be fully deprecated on February 16th, 2027.**

## What’s changing?

**The following [v1 OAuth API](https://developers.hubspot.com/docs/api-reference/auth-oauth-v1/guide) endpoints will be deprecated:**

- POST /v1/token
- GET /v1/access-tokens/{token}
- GET /v1/refresh-tokens/{token}
- DELETE /v1/refresh-tokens/{token}

These endpoints accept sensitive information and tokens in query parameters or the path, potentially exposing secrets in logs, browser history, or application telemetry.

**Important note:** The following v1 OAuth API endpoint: **DELETE /v1/refresh-tokens/{token}** , will be **replaced** by a new POST /oauth/2026-03/token/revoke endpoint.

## What does this mean for developers?

Review all applications and integrations using the deprecated v1 OAuth API endpoints. Migrate to the newer date-based versioned OAuth API endpoints:

- POST /oauth/2026-03/token
- POST /oauth/2026-03/token/introspect
- POST /oauth/2026-03/token/revoke

**as soon as possible.**

## Timeline and transition guidance

The v1 OAuth API endpoints will remain accessible until **February 16th, 2027.** All developers are strongly encouraged to complete migration to the date-based versioned OAuth API before this date to avoid service interruptions. [Our latest API documentation provides migration guidance and usage examples for the latest OAuth API endpoints](https://developers.hubspot.com/docs/api-reference/legacy/authentication/oauth-tokens/v1/migration-guide).

**Questions or comments?** Please join us below in the developer forum for a peer-to-peer discussion.  
[_\*Developer Changelog reference._](https://developers.hubspot.com/changelog/v1-oauth-api-deprecation)

---

<div class="post-metadata">

**Author:** ![lukeunigroup](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@lukeunigroup](https://community.hubspot.com/u/lukeunigroup)\
**Post date:** [October 5, 2026, 4:16pm UTC](https://community.hubspot.com/t/v1-oauth-api-deprecation/149267/2 "2026-10-05T16:16:25Z")

</div>

Is there any plan to migrate the nodejs api library to use this, or do we need to stop using that library? I found a couple of issues there, where this has already been asked, but there are no replies.

> <https://github.com/HubSpot/hubspot-api-nodejs/issues/689>
>
> Hello, 
> 
> just received this email from the HubSpot. I assume the library don't u…se those fresh APIs. Are there any plans on supporting it? Or the whole lib should be considered as deprecated?
> 
> thanks in advance
> 
> \<img width="515" height="689" alt="Image" src="https://github.com/user-attachments/assets/9c00859e-2b74-424f-82cb-dab2ed9396e9" /\>

> <https://github.com/HubSpot/hubspot-api-nodejs/issues/690>
>
> Will this SDK be migrated to the new 2026-03 endpoints?
> 
> https://developers.hubs…pot.com/docs/api-reference/legacy/authentication/oauth-tokens/v1/migration-guide