Migrate from the OAuth v1 API to the latest date-based versioned API

Open
#496 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
api, authentication, documentation

Research direction

Start with the generated OAuth client and its documentation, then compare the referenced OAuth v1 paths with HubSpot's linked migration guide. Update the client and docs to use the 2026-03 token, introspection, and revocation endpoints; done means no legacy OAuth v1 paths remain in the OAuth flow.

Written by the indexing model from the issue text.

Description

HubSpot is sunsetting the legacy OAuth v1 endpoints (/oauth/v1/token, /oauth/v1/access-tokens, etc.) on February 16, 2027 in favor of the new date-versioned endpoints (/oauth/2026-03/token, /oauth/2026-03/token/introspect, /oauth/2026-03/token/revoke).

This package still references/uses the old v1 paths in its OAuth client.

Please update the generated OAuth client + docs to the new 2026-03 version so users don't break after the sunset.
Link to the official migration guide

Thanks!

Dominant language
Python
Stars
434
Forks
126
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HubSpot/hubspot-api-python

All issues in HubSpot/hubspot-api-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.