Skip to content

PEP-1751: Deprecation notice for connectionManagement/accessToken endpoint#1857

Merged
Rachel-Codat merged 5 commits into
mainfrom
PEP-1751/deprecate-connectionmanagement-accesstoken
Jun 24, 2026
Merged

PEP-1751: Deprecation notice for connectionManagement/accessToken endpoint#1857
Rachel-Codat merged 5 commits into
mainfrom
PEP-1751/deprecate-connectionmanagement-accesstoken

Conversation

@Rachel-Codat

@Rachel-Codat Rachel-Codat commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

What

Adds a docs.codat.io changelog/blog entry announcing the deprecation of the public client route GET /companies/{companyId}/connectionManagement/accessToken in favour of the global GET /companies/{companyId}/accessToken endpoint.

Previously the only deprecation signal was the OAS deprecated: true marker (in codat-internal/oas, Codat-Platform.yaml) — no changelog or docs notice. This PR provides the published changelog notice required by PEP-1751.

Sunset date

2026-10-12 — the Q4 2026 enforcement date (first working day on/after Sat 10 Oct), per the change-policy deprecation schedule.

To land in the Q4 window this needs to be merged + live before the early-July quarterly developer email (~7 July 2026). If it slips past that, the date must move to the next quarter (2027-01-11).

Follow-ups (after merge — also add a deprecations Google Calendar entry)

  • API-docs notice beyond the spec marker — enhancing the endpoint description copy in the oas repo (reference/common/copy/connection-management/get-access-token.md) so the deprecation renders prominently on the API reference page.
  • Direct customer outreach to Toast (4ba960c6) and Bill360 (0059aab6) with the replacement endpoint + migration guidance.

Source: PEP-1632 auth-merge spike, Area 1b / 2.

🤖 Generated with Claude Code

Add a changelog/blog entry announcing deprecation of
GET /companies/{companyId}/connectionManagement/accessToken in favour of
the global GET /companies/{companyId}/accessToken endpoint.

Kept as draft: true pending an agreed sunset date (PEP-1751 AC).

PEP-1751

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 23, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
codat-docs Ready Ready Preview, Comment Jun 24, 2026 9:49am

Request Review

Rachel-Codat and others added 2 commits June 23, 2026 14:32
…10-12

Q4 2026 enforcement date (first working day on/after 10 Oct). Still draft
pending team confirmation and the early-July quarterly email cutoff.

PEP-1751

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Remove draft flag and pre-publish TODO note; team review handled via PR.

PEP-1751

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Rachel-Codat Rachel-Codat marked this pull request as ready for review June 23, 2026 13:34
…t endpoint

The new endpoint returns the token in the same accessToken field but also
adds expiresIn and tokenType. Make the migration note accurate.

PEP-1751

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rename blog entry to 260624 and update front-matter date accordingly.

PEP-1751

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

Link check results for preview deployment (https://codat-docs-git-PEP-1751-deprecate-connectionmanagement-accesstoken-codat.vercel.app):

[]

@avanjani-codat avanjani-codat left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, thanks Rachel

@Rachel-Codat Rachel-Codat merged commit 9243967 into main Jun 24, 2026
9 checks passed
@Rachel-Codat Rachel-Codat deleted the PEP-1751/deprecate-connectionmanagement-accesstoken branch June 24, 2026 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants