From 4cf806059b86878d13ba27be4247c0d5c876bf80 Mon Sep 17 00:00:00 2001
From: Rachel Davey <84862906+Rachel-Codat@users.noreply.github.com>
Date: Tue, 23 Jun 2026 14:22:56 +0100
Subject: [PATCH 1/5] docs(changelog): deprecation notice for
 connectionManagement/accessToken

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>
---
 ...tion-connection-management-access-token.md | 55 +++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 blog/260623-deprecation-connection-management-access-token.md

diff --git a/blog/260623-deprecation-connection-management-access-token.md b/blog/260623-deprecation-connection-management-access-token.md
new file mode 100644
index 000000000..663f950a9
--- /dev/null
+++ b/blog/260623-deprecation-connection-management-access-token.md
@@ -0,0 +1,55 @@
+---
+title: "Upcoming YYYY-MM-DD: Deprecation of the connection management access token endpoint"
+date: "2026-06-23"
+tags: ["Deprecation"]
+draft: true
+authors: rachelcodat
+---
+
+<!--
+TODO before publishing:
+  1. Agree the sunset date with the team (PEP-1751 acceptance criteria), following the
+     deprecation schedule in the change policy:
+     https://docs.codat.io/introduction/change-policy#deprecation-schedule
+  2. Replace every YYYY-MM-DD placeholder below (title + body) with the agreed date.
+  3. Set `date` to the publication date.
+  4. Remove the `draft: true` line.
+  5. Confirm with #team-documentation before publishing.
+-->
+
+On YYYY-MM-DD, Codat will deprecate the `connectionManagement/accessToken` endpoint used to generate company-specific connection management access tokens.
+
+<!--truncate-->
+
+Codat now supports a single, global company access token that provides seamless access across multiple products. To improve efficiency and consistency, we are deprecating the older connection-management-specific endpoint in favour of this global token.
+
+The following endpoint will be deprecated:
+
+```http
+GET /companies/{companyId}/connectionManagement/accessToken
+```
+
+## Action required
+
+If you are using the endpoint above, you will need to instead use the global company access token endpoint:
+
+```http
+GET /companies/{companyId}/accessToken
+```
+
+The replacement endpoint returns an access token in the same way and requires no additional configuration. Update your integration to call the new endpoint ahead of the deprecation date.
+
+## Expected impact if no action is taken
+
+After YYYY-MM-DD, calls to the deprecated endpoint will return a `404` error.
+
+```json
+{
+  "statusCode": 404,
+  "service": "PublicApi",
+  "error": "NotFound",
+  "correlationId": "2b60a2bafedd3238702c2186a2dc833f",
+  "canBeRetried": "Unknown",
+  "detailedErrorCode": 0
+}
+```

From f8c7aa4f15bb6aa792a3b48152883ded5e473e67 Mon Sep 17 00:00:00 2001
From: Rachel Davey <84862906+Rachel-Codat@users.noreply.github.com>
Date: Tue, 23 Jun 2026 14:32:24 +0100
Subject: [PATCH 2/5] docs(changelog): set connectionManagement/accessToken
 sunset to 2026-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>
---
 ...tion-connection-management-access-token.md | 20 ++++++++++---------
 1 file changed, 11 insertions(+), 9 deletions(-)

diff --git a/blog/260623-deprecation-connection-management-access-token.md b/blog/260623-deprecation-connection-management-access-token.md
index 663f950a9..41f4ad7b8 100644
--- a/blog/260623-deprecation-connection-management-access-token.md
+++ b/blog/260623-deprecation-connection-management-access-token.md
@@ -1,5 +1,5 @@
 ---
-title: "Upcoming YYYY-MM-DD: Deprecation of the connection management access token endpoint"
+title: "Upcoming 2026-10-12: Deprecation of the connection management access token endpoint"
 date: "2026-06-23"
 tags: ["Deprecation"]
 draft: true
@@ -8,16 +8,18 @@ authors: rachelcodat
 
 <!--
 TODO before publishing:
-  1. Agree the sunset date with the team (PEP-1751 acceptance criteria), following the
-     deprecation schedule in the change policy:
-     https://docs.codat.io/introduction/change-policy#deprecation-schedule
-  2. Replace every YYYY-MM-DD placeholder below (title + body) with the agreed date.
-  3. Set `date` to the publication date.
-  4. Remove the `draft: true` line.
+  1. Confirm the 2026-10-12 sunset date with the team (PEP-1751 acceptance criteria).
+     This is the Q4 2026 enforcement date (first working day on/after Sat 10 Oct).
+     The changelog entry MUST be live before the early-July quarterly developer email
+     (practically ~7 July 2026) to make the Q4 window; otherwise the next date is
+     2027-01-11. See https://docs.codat.io/using-the-api/change-policy#deprecation-schedule
+  2. Set `date` to the publication date.
+  3. Remove the `draft: true` line.
+  4. Add a corresponding entry to the deprecations Google Calendar.
   5. Confirm with #team-documentation before publishing.
 -->
 
-On YYYY-MM-DD, Codat will deprecate the `connectionManagement/accessToken` endpoint used to generate company-specific connection management access tokens.
+On 2026-10-12, Codat will deprecate the `connectionManagement/accessToken` endpoint used to generate company-specific connection management access tokens.
 
 <!--truncate-->
 
@@ -41,7 +43,7 @@ The replacement endpoint returns an access token in the same way and requires no
 
 ## Expected impact if no action is taken
 
-After YYYY-MM-DD, calls to the deprecated endpoint will return a `404` error.
+After 2026-10-12, calls to the deprecated endpoint will return a `404` error.
 
 ```json
 {

From 983a5c530b3392ad3f08c55778fe477fb4ef340a Mon Sep 17 00:00:00 2001
From: Rachel Davey <84862906+Rachel-Codat@users.noreply.github.com>
Date: Tue, 23 Jun 2026 14:34:19 +0100
Subject: [PATCH 3/5] docs(changelog): publish connectionManagement/accessToken
 deprecation

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>
---
 ...precation-connection-management-access-token.md | 14 --------------
 1 file changed, 14 deletions(-)

diff --git a/blog/260623-deprecation-connection-management-access-token.md b/blog/260623-deprecation-connection-management-access-token.md
index 41f4ad7b8..917e688a2 100644
--- a/blog/260623-deprecation-connection-management-access-token.md
+++ b/blog/260623-deprecation-connection-management-access-token.md
@@ -2,23 +2,9 @@
 title: "Upcoming 2026-10-12: Deprecation of the connection management access token endpoint"
 date: "2026-06-23"
 tags: ["Deprecation"]
-draft: true
 authors: rachelcodat
 ---
 
-<!--
-TODO before publishing:
-  1. Confirm the 2026-10-12 sunset date with the team (PEP-1751 acceptance criteria).
-     This is the Q4 2026 enforcement date (first working day on/after Sat 10 Oct).
-     The changelog entry MUST be live before the early-July quarterly developer email
-     (practically ~7 July 2026) to make the Q4 window; otherwise the next date is
-     2027-01-11. See https://docs.codat.io/using-the-api/change-policy#deprecation-schedule
-  2. Set `date` to the publication date.
-  3. Remove the `draft: true` line.
-  4. Add a corresponding entry to the deprecations Google Calendar.
-  5. Confirm with #team-documentation before publishing.
--->
-
 On 2026-10-12, Codat will deprecate the `connectionManagement/accessToken` endpoint used to generate company-specific connection management access tokens.
 
 <!--truncate-->

From ddb3718d4529a65f1378873d177b1f3103e44f60 Mon Sep 17 00:00:00 2001
From: Rachel Davey <84862906+Rachel-Codat@users.noreply.github.com>
Date: Tue, 23 Jun 2026 14:48:44 +0100
Subject: [PATCH 4/5] docs(changelog): clarify response-shape difference for
 the replacement 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>
---
 blog/260623-deprecation-connection-management-access-token.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/blog/260623-deprecation-connection-management-access-token.md b/blog/260623-deprecation-connection-management-access-token.md
index 917e688a2..bafb3a73c 100644
--- a/blog/260623-deprecation-connection-management-access-token.md
+++ b/blog/260623-deprecation-connection-management-access-token.md
@@ -25,7 +25,7 @@ If you are using the endpoint above, you will need to instead use the global com
 GET /companies/{companyId}/accessToken
 ```
 
-The replacement endpoint returns an access token in the same way and requires no additional configuration. Update your integration to call the new endpoint ahead of the deprecation date.
+The access token is returned in the same `accessToken` field, so if you read that field you can switch to the new endpoint with no further changes. The replacement response additionally includes `expiresIn` (seconds until the token expires) and `tokenType` (for example, `Bearer`). Update your integration to call the new endpoint ahead of the deprecation date.
 
 ## Expected impact if no action is taken
 

From b35a9787a3a95a68a0272f51749617601ba4dce7 Mon Sep 17 00:00:00 2001
From: Rachel Davey <84862906+Rachel-Codat@users.noreply.github.com>
Date: Wed, 24 Jun 2026 10:46:15 +0100
Subject: [PATCH 5/5] docs(changelog): set publication date to 2026-06-24

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>
---
 ...=> 260624-deprecation-connection-management-access-token.md} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename blog/{260623-deprecation-connection-management-access-token.md => 260624-deprecation-connection-management-access-token.md} (98%)

diff --git a/blog/260623-deprecation-connection-management-access-token.md b/blog/260624-deprecation-connection-management-access-token.md
similarity index 98%
rename from blog/260623-deprecation-connection-management-access-token.md
rename to blog/260624-deprecation-connection-management-access-token.md
index bafb3a73c..323f9563d 100644
--- a/blog/260623-deprecation-connection-management-access-token.md
+++ b/blog/260624-deprecation-connection-management-access-token.md
@@ -1,6 +1,6 @@
 ---
 title: "Upcoming 2026-10-12: Deprecation of the connection management access token endpoint"
-date: "2026-06-23"
+date: "2026-06-24"
 tags: ["Deprecation"]
 authors: rachelcodat
 ---