diff --git a/fix_banners.ps1 b/fix_banners.ps1
new file mode 100644
index 0000000000..737a07f684
--- /dev/null
+++ b/fix_banners.ps1
@@ -0,0 +1,53 @@
+$files = Get-ChildItem -Path src -Recurse -File -Include '*.md','*.markdown'
+$changed = 0
+
+$link = '<a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a>'
+$footer = "  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>`n  <p>Learn more in the $link</p>`n</div>"
+
+function MakeBanner($dep, $unsup, $content) {
+    $lines = @('<div class="alert alert-danger">', '  <p><strong>This API has been deprecated.</strong></p>')
+    if ($dep)   { $lines += "  <p>Deprecation Date: $dep</p>" }
+    if ($unsup) { $lines += "  <p>Unsupported Date: $unsup</p>" }
+    if ($content) { $lines += "  <p>$($content.Trim())</p>" }
+    $lines += "  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>"
+    $lines += "  <p>Learn more in the $link</p>"
+    $lines += '</div>'
+    return $lines -join "`n"
+}
+
+foreach ($f in $files) {
+    $raw = [System.IO.File]::ReadAllText($f.FullName, [System.Text.Encoding]::UTF8)
+    if (-not ($raw -match 'include deprecation-alert')) { continue }
+
+    $new = $raw
+
+    # Case 1: capture block + date + unsupported + content
+    $new = [regex]::Replace($new,
+        '(?s)\{%\s*capture\s+deprecation_content\s*%\}(.*?)\{%\s*endcapture\s*%\}\s*\n\s*\{%\s*include deprecation-alert\.html\s+deprecation_date="([^"]+)"\s+unsupported_date="([^"]+)"\s+content=deprecation_content\s*%\}',
+        { param($m)
+          return MakeBanner $m.Groups[2].Value $m.Groups[3].Value $m.Groups[1].Value
+        })
+
+    # Case 2: capture block + date + content (no unsupported)
+    $new = [regex]::Replace($new,
+        '(?s)\{%\s*capture\s+deprecation_content\s*%\}(.*?)\{%\s*endcapture\s*%\}\s*\n\s*\{%\s*include deprecation-alert\.html\s+deprecation_date="([^"]+)"\s+content=deprecation_content\s*%\}',
+        { param($m)
+          return MakeBanner $m.Groups[2].Value $null $m.Groups[1].Value
+        })
+
+    # Case 3: only deprecation_date
+    $new = [regex]::Replace($new,
+        '\{%\s*include deprecation-alert\.html\s+deprecation_date="([^"]+)"\s*%\}',
+        { param($m) return MakeBanner $m.Groups[1].Value $null $null })
+
+    # Case 4: simple include (no params)
+    $new = $new -replace '(?m)^\s*\{%\s*include deprecation-alert\.html\s*%\}\s*$', (MakeBanner $null $null $null)
+
+    if ($new -ne $raw) {
+        [System.IO.File]::WriteAllText($f.FullName, $new, [System.Text.Encoding]::UTF8)
+        $changed++
+        Write-Output "Fixed: $($f.FullName.Replace((Get-Location).Path + '\','').Replace('\','/'))"
+    }
+}
+Write-Output ""
+Write-Output "Total files changed: $changed"
diff --git a/src/api-explorer/v3-0/AttendeeTypes.markdown b/src/api-explorer/v3-0/AttendeeTypes.markdown
index e87e58a877..5924bbd972 100644
--- a/src/api-explorer/v3-0/AttendeeTypes.markdown
+++ b/src/api-explorer/v3-0/AttendeeTypes.markdown
@@ -1,15 +1,18 @@
----
+---
 title: Attendee Types
 layout: reference
 reference-type: swagger
 ---
 
-{% capture deprecation_content %}
-* POST `/expense/attendeetypes`
-* DELETE `/expense/attendeetypes/{id}`
-{% endcapture %}
-
-{% include deprecation-alert.html deprecation_date="05/19/2016" unsupported_date="11/19/2016" content=deprecation_content %}
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Deprecation Date: 05/19/2016</p>
+  <p>Unsupported Date: 11/19/2016</p>
+  <p>* POST `/expense/attendeetypes`
+* DELETE `/expense/attendeetypes/{id}`</p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 
 
 {% swagger /api-explorer/v3-0/AttendeeTypes.swagger2.json %}
diff --git a/src/api-explorer/v3-0/Attendees.markdown b/src/api-explorer/v3-0/Attendees.markdown
index cab793a3f2..ec66b12968 100644
--- a/src/api-explorer/v3-0/Attendees.markdown
+++ b/src/api-explorer/v3-0/Attendees.markdown
@@ -1,13 +1,16 @@
----
+---
 title: Attendees
 layout: reference
 reference-type: swagger
 ---
 
-{% capture deprecation_content %}
-* DELETE `/expense/attendees/{id}`
-{% endcapture %}
-
-{% include deprecation-alert.html deprecation_date="05/19/2016" unsupported_date="11/19/2016" content=deprecation_content %}
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Deprecation Date: 05/19/2016</p>
+  <p>Unsupported Date: 11/19/2016</p>
+  <p>* DELETE `/expense/attendees/{id}`</p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 
 {% swagger /api-explorer/v3-0/Attendees.swagger2.json %}
diff --git a/src/api-explorer/v3-0/ListItems.markdown b/src/api-explorer/v3-0/ListItems.markdown
index 99327fab58..61a64ecb92 100644
--- a/src/api-explorer/v3-0/ListItems.markdown
+++ b/src/api-explorer/v3-0/ListItems.markdown
@@ -1,9 +1,11 @@
----
+---
 title: List Items
 layout: reference
 reference-type: swagger
 ---
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 {% swagger /api-explorer/v3-0/ListItems.swagger2.json %}
diff --git a/src/api-explorer/v3-0/Lists.markdown b/src/api-explorer/v3-0/Lists.markdown
index 31fce8de1d..d6765eda04 100644
--- a/src/api-explorer/v3-0/Lists.markdown
+++ b/src/api-explorer/v3-0/Lists.markdown
@@ -1,9 +1,11 @@
----
+---
 title: Lists
 layout: reference
 reference-type: swagger
 ---
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 {% swagger /api-explorer/v3-0/Lists.swagger2.json %}
diff --git a/src/api-explorer/v3-0/Users.markdown b/src/api-explorer/v3-0/Users.markdown
index e0682e4598..a332c53fd1 100644
--- a/src/api-explorer/v3-0/Users.markdown
+++ b/src/api-explorer/v3-0/Users.markdown
@@ -4,6 +4,11 @@ layout: reference
 reference-type: swagger
 ---
 
-{% include deprecation-alert.html deprecation_date="08/22/2021" content=deprecation_content %}
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Deprecation Date: 08/22/2021</p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 
 {% swagger /api-explorer/v3-0/Users.swagger2.json %}
diff --git a/src/api-guides/invoice/payment-provider-integration.md b/src/api-guides/invoice/payment-provider-integration.md
index 200a89c996..2bccb7eb84 100644
--- a/src/api-guides/invoice/payment-provider-integration.md
+++ b/src/api-guides/invoice/payment-provider-integration.md
@@ -88,7 +88,7 @@ Editable By:      This depends on the customer configuration
 
 ### <a name="Overview-Scopes-and-Obtaining-Invoices-pending-payment"></a>Overview Scopes and Obtaining Invoices pending payment
 
-[Overview, Scopes, an Obtaining Invoices pending payment](/api-reference/invoice/v1.invoice-pay.html)
+[Overview, Scopes, an Obtaining Invoices pending payment](/api-reference/invoice/v4.invoice-pay.html)
 
 ### <a name="Discounts"></a>Discounts on invoices
 
diff --git a/src/api-reference/authentication/app-center-learn-more.md b/src/api-reference/authentication/app-center-learn-more.md
index fc52df885d..919cfa74e5 100644
--- a/src/api-reference/authentication/app-center-learn-more.md
+++ b/src/api-reference/authentication/app-center-learn-more.md
@@ -1,4 +1,4 @@
----
+---
 title: Learn More About Scopes
 layout: reference
 ---
@@ -44,7 +44,7 @@ Scope|User Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
 `expense.config.expensetypes.restricted.read`<a name="expense.config.policies.restricted.read"></a>|Get a list of expense types applicable to a user based on a policy|[Expense Configuration v4](/api-reference/expense/expense-config/v4.expense.config.html)
 `expense.config.paymenttypes.restricted.read`<a name="expense.config.policies.restricted.read"></a>|Get a list of all payment types applicable to a user|[Expense Configuration v4](/api-reference/expense/expense-config/v4.expense.config.html)
 `expense.exchangerate.writeonly` <a name="expense-exchangerate-writeonly"></a> |Create custom exchange rates|[Exchange Rate v4](/api-reference/expense/exchange-rate/v4.exchange-rate.html)
-`expense.report.read` <a name="expense-report-read"></a> |Get information about expense reports|[Comments v4](/api-reference/expense/expense-report/v4.comments.html), [Reports v4](/api-reference/expense/expense-report/v4.reports.html), [Allocations v4](/api-reference/expense/expense-report/v4.allocations.html), [Expenses v4](/api-reference/expense/expense-report/v4.expenses.html), [Itemizations v4](/api-reference/expense/expense-report/v4.expense-itemization.html), [Attendee Associations v4](/api-reference/expense/expense-report/v4.expense-attendee-associations.html), [Exceptions v4](/api-reference/expense/expense-report/v4.exceptions.html), [Expense Tax v4](/api-reference/expense/expense-report/v4.expense-tax.html), [Cash Advance Associations v4](/api-reference/expense/expense-report/v4.expense-cash-advance-associations.html)
+`expense.report.read` <a name="expense-report-read"></a> |Get information about expense reports|[Comments v4](/api-reference/expense/expense-report/v4.comments.html), [Reports v4](/api-reference/expense/expense-report/v4.reports.html), [Allocations v4](/api-reference/expense/expense-report/v4.allocations.html), [Expenses v4](/api-reference/expense/expense-report/v4.expenses.html), [Itemizations v4](/api-reference/expense/expense-report/expense-itemization.html), [Attendee Associations v4](/api-reference/expense/expense-report/v4.expense-attendee-associations.html), [Exceptions v4](/api-reference/expense/expense-report/v4.exceptions.html), [Expense Tax v4](/api-reference/expense/expense-report/v4.expense-tax.html), [Cash Advance Associations v4](/api-reference/expense/expense-report/v4.expense-cash-advance-associations.html)
 `expense.report.readwrite` <a name="expense-report-readwrite"></a> |Read and write expense report headers|[Comments v4](/api-reference/expense/expense-report/v4.comments.html), [Reports v4](/api-reference/expense/expense-report/v4.reports.html), [Allocations v4](/api-reference/expense/expense-report/v4.allocations.html), [Expenses v4](/api-reference/expense/expense-report/v4.expenses.html), [Attendee Associations v4](/api-reference/expense/expense-report/v4.expense-attendee-associations.html), [Exceptions v4](/api-reference/expense/expense-report/v4.exceptions.html), [Expense Tax v4](/api-reference/expense/expense-report/v4.expense-tax.html), [Cash Advance Associations v4](/api-reference/expense/expense-report/v4.expense-cash-advance-associations.html)
 `expense.report.tax.readwrite` <a name="expense-report-tax-readwrite"></a> |Read and Write information about tax details of an expense on a report|[Expense Tax v4](/api-reference/expense/expense-report/v4.expense-tax.html)
 `expense.report.workflowstatus.write` <a name="expense-report-workflowstatus-write"></a> |Approve or Send Back the Report in the workflow|[Comments v4](/api-reference/expense/expense-report/v4.comments.html), [Reports v4](/api-reference/expense/expense-report/v4.reports.html)
@@ -71,7 +71,7 @@ Scope|User Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
 `INVPO` <a name="invpo"></a> |Create or update purchase orders|[Invoice Purchase Orders v3](/api-reference/invoice/v3.purchase-order.html)
 `INVTV` <a name="invtv"></a> |View tax invoices and update validation status|[Invoice Sales Tax Validation Request v3](/api-reference/invoice/v3.sales-tax-validation.html)
 `INVVEN` <a name="invven"></a> |Vendors search and retrieve list of vendors|[Invoice Vendor v3](/api-reference/invoice/v3.vendor.html), [Invoice Vendor Group Swagger](/api-explorer/v3-0/VendorGroup.html), [Invoice Vendor Bank Swagger](/api-explorer/v3-0/VendorBank.html)[Vendor 3.1](/api-reference/invoice/v3.1.vendor.html)
-`ITINER` <a name="itiner"></a> |Get, add, or update travel itineraries and bookings|[Itinerary Web Service](/api-reference/travel/itinerary-tmc-thirdparty/), [Travel-Booking Resource](/api-reference/travel/itinerary/booking/booking-resource.html), [Itinerary Service](/api-reference/travel/itinerary/itinerary.html), [Travel-Trips v1.1](/api-reference/travel/itinerary/trip/trip-resource.html), [Travel Services](/api-reference/travel/travel.html), [Trip Approval v1](/api-reference/travel/trip-approval/trip-approval-resource.html)
+`ITINER` <a name="itiner"></a> |Get, add, or update travel itineraries and bookings|[Itinerary Web Service](/api-reference/travel/itinerary-tmc-thirdparty/), [Travel-Booking Resource](/api-reference/travel/itinerary/booking/booking-resource.html), [Itinerary Service](/api-reference/travel/itinerary/itinerary.html), [Travel-Trips v1.1](/api-reference/travel/itinerary/trip/trip-resource.html), [Trip Approval v1](/api-reference/travel/itinerary/trip/trip-resource.html)
 `LIST` <a name="list"></a> |Use and update drop-down lists configured by your company|[List Item v3](/api-reference/common/list-item/v3.list-item.html), [List v1](/api-reference/common/list-item/v1.list-item.html), [List v1 Resource](/api-reference/common/list-item/v1.list-resource.html), [Get List of List v1](/api-reference/common/list-item/v1.list-resource-get.html), [Post New List v1](/api-reference/common/list-item/v1.list-resource-post.html), [Budget v4](/api-reference/budget/getting-started.html)
 `locality.read` <a name="locality-read"></a> |Allows the application to only view location-related information using the SAP Concur Localities API|[Localities v5](/api-reference/common/locations/v5.localities.html)
 `locate.location.read` <a name="locate-location-read"></a> |Allows the application to only view the SAP  Concur Locate user location|[User Location v4](/api-reference/locate/v4.userLocations.html)
@@ -83,7 +83,7 @@ Scope|User Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
 `purchaserequest.read` <a name="purchaserequest-read"></a> |Allows you to retrieve purchase requests|[Purchase Request v4](/api-reference/invoice/v4.purchase-request-get-started.html)
 `purchaserequest.write` <a name="purchaserequest-write"></a> |Allows you to create new purchase requests|[Purchase Request v4](/api-reference/invoice/v4.purchase-request-get-started.html)
 `quickexpense.writeonly` <a name="quickexpense-writeonly"></a> |Write quick expense|[Quick Expense v4](/api-reference/expense/quick-expense/v4.quick-expense.html)
-`RCTIMG` <a name="rctimg"></a> |Add or update receipt and OCR images|[Receipt Image v3](/api-reference/image/)
+`RCTIMG` <a name="rctimg"></a> |Add or update receipt and OCR images|[Receipt Image v3](/api-reference/image/v3.image.html)
 `receipts.read` <a name="receipts-read"></a> |Read receipt data|[Receipts v4](/api-reference/receipts/get-started.html),[Document Compliance Gateway v4](/api-reference/document-compliance-gateway/V4.document-compliance-gateway.html)
 `receipts.write` <a name="receipts-write"></a> |Read receipt data and post receipts|[Receipts v4](/api-reference/receipts/get-started.html),[Document Compliance Gateway v4](/api-reference/document-compliance-gateway/V4.document-compliance-gateway.html)
 `receipts.writeonly` <a name="receipts-writeonly"></a> |Post receipts on your behalf|[Receipts v4](/api-reference/receipts/get-started.html), [Quick Expense v4](/api-reference/expense/quick-expense/v4.quick-expense.html)
@@ -119,7 +119,7 @@ Scope|User Description&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs
 `TRVPRF` <a name="trvprf"></a> |Access and update Concur Travel profile information|[Travel Profile v2](/api-reference/travel-profile/v2.profile-service.html), [Travel Profile v2 Resource](/api-reference/travel-profile/v2.profile-resource.html)
 `TRVPTS` <a name="trvpts"></a> |Access user balances and post travel points redemptions|[Travel Profile v1 Travel Points](/api-reference/travel-profile/v1.loyalty-program-resource.html)
 `TRVREQ` <a name="trvreq"></a> |Add, update, or delete authorization requests|[Travel Request v3](/api-reference/request/v3.request.html)
-`TWS` <a name="tws"></a> |Approve or reject travel itineraries|[Trip Approvals](/api-reference/travel/trip-approval/trip-approval-resource.html)
+`TWS` <a name="tws"></a> |Approve or reject travel itineraries|[Trip Approvals](/api-reference/travel/itinerary/trip/trip-resource.html)
 `UNUTX` <a name="unutx"></a> |Unused tickets|[Travel Profile v2 Unused Tickets](/api-reference/travel-profile/v2.profile-resource.html#UnusedTickets)
 `user.read` <a name="user-read"></a> |Read profile information|[Profile](/api-reference/profile/v1.getting-started.html), [User API (Profile v1)](/api-reference/profile/v1.user.html), [Comments v4](/api-reference/expense/expense-report/v4.comments.html), [Reports v4](/api-reference/expense/expense-report/v4.reports.html), [Allocations v4](/api-reference/expense/expense-report/v4.allocations.html), [Expenses v4](/api-reference/expense/expense-report/v4.expenses.html), [Quick Expense v4](/api-reference/expense/quick-expense/v4.quick-expense.html), [Expense Configuration v4](/api-reference/expense/expense-config/v4.expense.config.html)
 `user.write` <a name="user-write"></a> |Read and update profile information|[Profile](/api-reference/profile/v1.getting-started.html), [User API (Profile v1)](/api-reference/profile/v1.user.html)
diff --git a/src/api-reference/authentication/authorization-pre-2017.markdown b/src/api-reference/authentication/authorization-pre-2017.markdown
index 532e1a842d..6d594bcef5 100644
--- a/src/api-reference/authentication/authorization-pre-2017.markdown
+++ b/src/api-reference/authentication/authorization-pre-2017.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Pre-2017 Authorization (Deprecated)
 layout: reference
 redirect_from:
@@ -7,15 +7,15 @@ redirect_from:
 
 # Pre-2017 Authorization (Deprecated)
 
-{% capture deprecation_content %}
-
-If you are a new partner or an existing one creating a new app, please refer to the [new authentication version documentation](/api-reference/authentication/getting-started.html).
-
-Please contact your Partner Enablement representative before starting any new development to ensure a smooth and successful certification process.
-
-{% endcapture %}
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Deprecation Date: 02/04/2017</p>
+  <p>If you are a new partner or an existing one creating a new app, please refer to the [new authentication version documentation](/api-reference/authentication/getting-started.html).
 
-{% include deprecation-alert.html deprecation_date="02/04/2017" content=deprecation_content %}
+Please contact your Partner Enablement representative before starting any new development to ensure a smooth and successful certification process.</p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 
 ## Access tokens <a name="access-tokens"></a>
 An access token is a long-lived token used to make API calls.
diff --git a/src/api-reference/budget/v4.budget-header.md b/src/api-reference/budget/v4.budget-header.md
index 75b7a881ed..bbd0d67adb 100644
--- a/src/api-reference/budget/v4.budget-header.md
+++ b/src/api-reference/budget/v4.budget-header.md
@@ -1,4 +1,4 @@
----
+---
 title: Budget v4 - Budget Item
 layout: reference
 ---
@@ -1577,7 +1577,7 @@ Name|Type|Format|Description
 Name|Type|Format|Description
 ---|---|---|---
 `featureTypeCode`|`string`|-|**Required** The product that this expense type applies to: Purchase Request, Invoice (Payment Request), Expense, or Request. Supported values: `PURCHASE_REQUEST`, `PAYMENT_REQUEST`, `EXPENSE`, `REQUEST`
-`expenseTypeCode`|`string`|-|**Required** The alphanumeric code that describes an expense type. (Example: `MEALS`, `AC_CATER`) Valid expense type codes are returned by the GET /budgetCategory/expenseType method described in the [Budget Category service](/api-reference/budget/budget-category.html).
+`expenseTypeCode`|`string`|-|**Required** The alphanumeric code that describes an expense type. (Example: `MEALS`, `AC_CATER`) Valid expense type codes are returned by the GET /budgetCategory/expenseType method described in the [Budget Category service](/api-reference/budget/v4.budget-category.html).
 `name`|`string`|-|**READ ONLY** The name for this expense type if it maps to an expense type set up in your SAP Concur product(s).
 `id`|`string`|-|The budget service's key for this object.
 
diff --git a/src/api-reference/callouts/request-validation.markdown b/src/api-reference/callouts/request-validation.markdown
index df3ed28179..2f2c6e9870 100644
--- a/src/api-reference/callouts/request-validation.markdown
+++ b/src/api-reference/callouts/request-validation.markdown
@@ -1,12 +1,14 @@
----
+---
 title: Travel Request Validation
 layout: reference
 ---
 
 # Travel Request Validation
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 Requests in the SAP Concur platform can be validated in an external system by using a combination of callouts and web services.  
 
 This guide provides a step by step overview of how to set up and use the external validation functionality for Requests. This guide does not provide instruction on the process of programming the application connector, but provides an overview of the required functionality.
diff --git a/src/api-reference/common/list-item/v1.list-item.markdown b/src/api-reference/common/list-item/v1.list-item.markdown
index 79b51b9b30..28baed10ce 100644
--- a/src/api-reference/common/list-item/v1.list-item.markdown
+++ b/src/api-reference/common/list-item/v1.list-item.markdown
@@ -1,4 +1,4 @@
----
+---
 title: List Item Web Service v1
 layout: reference
 
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # List Item Web Service v1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 ## Description
 
 The Concur List Item web service provides an automated solution to clients who would like to add, update or delete list items. This web service solves several business problems:
diff --git a/src/api-reference/common/list-item/v1.list-resource-get.markdown b/src/api-reference/common/list-item/v1.list-resource-get.markdown
index d88990679d..231fb5296c 100644
--- a/src/api-reference/common/list-item/v1.list-resource-get.markdown
+++ b/src/api-reference/common/list-item/v1.list-resource-get.markdown
@@ -1,4 +1,4 @@
----
+---
 title: List Item Web Service v1 - Get a list of lists
 layout: reference
 
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # List Item Web Service v1 - Get a list of lists
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 This resource supports the following GET actions:
 
 * Get List of Lists
diff --git a/src/api-reference/common/list-item/v1.list-resource-post.markdown b/src/api-reference/common/list-item/v1.list-resource-post.markdown
index ed2c37d8e8..8bef617d53 100644
--- a/src/api-reference/common/list-item/v1.list-resource-post.markdown
+++ b/src/api-reference/common/list-item/v1.list-resource-post.markdown
@@ -1,4 +1,4 @@
----
+---
 title: List Item Web Service v1 - Post new list items
 layout: reference
 
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # List Item Web Service v1 - Post new list items
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 This resource supports the following POST actions:
 
 * Post new list item
diff --git a/src/api-reference/common/list-item/v1.list-resource.markdown b/src/api-reference/common/list-item/v1.list-resource.markdown
index 21996eb55a..63b640bf4a 100644
--- a/src/api-reference/common/list-item/v1.list-resource.markdown
+++ b/src/api-reference/common/list-item/v1.list-resource.markdown
@@ -1,4 +1,4 @@
----
+---
 title: List Item Web Service v1 - List Resource
 layout: reference
 
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # List Item Web Service v1 - List Resource
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 ## Description
 
 The configured lists in the SAP Concur platform. Can be single or multiple level lists.
diff --git a/src/api-reference/common/list-item/v3.list-item.markdown b/src/api-reference/common/list-item/v3.list-item.markdown
index b60f37acc2..94ef9f93bb 100644
--- a/src/api-reference/common/list-item/v3.list-item.markdown
+++ b/src/api-reference/common/list-item/v3.list-item.markdown
@@ -1,12 +1,14 @@
----
+---
 title: List Item v3
 layout: reference
 ---
 
 # List Item v3
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 The List Item API provides an automated solution to clients who would like to add, update, or delete list items. Use of the API is subject to some limitations on the volume of List data. You may need to manage the initial load of large volumes of data via a file import due to capacity limitations. This is also true if ongoing maintenance of List values involves a large volume.
 
 1.0 documentation is available [here](/api-reference/common/list-item/v1.list-item.html)
diff --git a/src/api-reference/common/lists/v3.lists.markdown b/src/api-reference/common/lists/v3.lists.markdown
index 0c7e763482..0d7447a12b 100644
--- a/src/api-reference/common/lists/v3.lists.markdown
+++ b/src/api-reference/common/lists/v3.lists.markdown
@@ -1,12 +1,14 @@
----
+---
 title: Lists v3
 layout: reference
 ---
 
 # Lists v3
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 The Lists API allows you to view your configured lists within SAP Concur products, and create new lists. The lists are shared between multiple SAP Concur products. Use the [List Items API](/api-reference/common/list-item/v3.list-item.html) to manage the items in the lists.
 
 ## Limitations
@@ -203,7 +205,14 @@ fetch('https://www.concursolutions.com/api/v3.0/common/lists/{id}',
 
 ## Update List <a name="put"></a>
 
->**DEPRECATED**: 05/19/2016 UNSUPPORTED: 11/19/2016. Updates list specified in the URL. Only the fields provided in the supplied object will be updated, missing fields will not be altered.
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Deprecation Date: 05/19/2016</p>
+  <p>Unsupported Date: 11/19/2016</p>
+  <p>Updates list specified in the URL. Only the fields provided in the supplied object will be updated, missing fields will not be altered.</p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 
 ### Parameters
 
diff --git a/src/api-reference/common/locations/v5.localities.md b/src/api-reference/common/locations/v5.localities.md
index 3ba033d130..910d1337ef 100644
--- a/src/api-reference/common/locations/v5.localities.md
+++ b/src/api-reference/common/locations/v5.localities.md
@@ -1,4 +1,4 @@
----
+---
 title: Localities v5
 layout: reference
 ---
@@ -9,7 +9,7 @@ This API acts as a single source of truth for location-related information, incl
 
 ## Prior Versions
 
-* Locations v3 documentation is available [here](https://developer.concur.com/api-reference/common/locations/v3.locations.html)
+* Locations v3 documentation is available [here](https://developer.concur.com/api-reference/common/locations/v3.locations.html.html)
 
 ## <a name="limitations"></a>Limitations
 
diff --git a/src/api-reference/direct-connects/ground-transportation/update-reservation-travel.markdown b/src/api-reference/direct-connects/ground-transportation/update-reservation-travel.markdown
index 58c6c9e30b..8793e48888 100644
--- a/src/api-reference/direct-connects/ground-transportation/update-reservation-travel.markdown
+++ b/src/api-reference/direct-connects/ground-transportation/update-reservation-travel.markdown
@@ -1,12 +1,14 @@
----
+---
 title: Direct Connect - Ground Transportation - Update reservation with Travel
 layout: reference
 ---
 
 # Update reservation with Travel
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 This request is sent when the ground transportation service provider needs to send an update to the reservation to Travel.
 
 ## Limitations
diff --git a/src/api-reference/direct-connects/hotel.markdown b/src/api-reference/direct-connects/hotel.markdown
index 92e51a37d1..67377fefe7 100644
--- a/src/api-reference/direct-connects/hotel.markdown
+++ b/src/api-reference/direct-connects/hotel.markdown
@@ -1,12 +1,14 @@
----
+---
 title: Direct Connect - Hotel v1
 layout: reference
 ---
 
 # Direct Connect - Hotel v1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 ## Description
 
 The Hotel Services Direct Connect provides a method for Travel users to access hotel inventory.
diff --git a/src/api-reference/expense/attendee-types/v1.attendee-types.markdown b/src/api-reference/expense/attendee-types/v1.attendee-types.markdown
index dc3defb961..ee0062de24 100644
--- a/src/api-reference/expense/attendee-types/v1.attendee-types.markdown
+++ b/src/api-reference/expense/attendee-types/v1.attendee-types.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Attendee Types v1
 layout: reference
 redirect_from:
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # Attendee Types v1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 ## Description
 
 The Attendee Type resource represents the type of attendee as configured in Concur. Retrieves the list of attendee types for the company.
diff --git a/src/api-reference/expense/attendees/v1.attendees.markdown b/src/api-reference/expense/attendees/v1.attendees.markdown
index 4df404b8ec..348c7ffef3 100644
--- a/src/api-reference/expense/attendees/v1.attendees.markdown
+++ b/src/api-reference/expense/attendees/v1.attendees.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Attendees v1
 layout: reference
 redirect_from:
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # Attendees v1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 The Shared attendees in the Concur company. Attendees added using this web service are added to the Shared Attendee List (owned by the System and available to all users). This resource can't be used to create attendees on a Private List.
 
 ## Limitations
diff --git a/src/api-reference/expense/attendees/v1dot1.attendees.markdown b/src/api-reference/expense/attendees/v1dot1.attendees.markdown
index a31275f6c8..98f21564a2 100644
--- a/src/api-reference/expense/attendees/v1dot1.attendees.markdown
+++ b/src/api-reference/expense/attendees/v1dot1.attendees.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Attendees v1.1
 layout: reference
 redirect_from:
@@ -6,9 +6,11 @@ redirect_from:
 ---
 
 # Attendees v1.1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 Creates or updates one or more attendee records for the specified expense entry. Attendees are additional people that benefitted from this expense.
 
 **Attendee External ID Considerations**
diff --git a/src/api-reference/expense/attendees/v2.attendees.markdown b/src/api-reference/expense/attendees/v2.attendees.markdown
index ea637cbf98..4766f2281b 100644
--- a/src/api-reference/expense/attendees/v2.attendees.markdown
+++ b/src/api-reference/expense/attendees/v2.attendees.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Attendees v2
 layout: reference
 redirect_from:
@@ -8,9 +8,11 @@ redirect_from:
 ---
 
 # Attendees v2
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 The attendees in the Concur company. This resource can be used to retrieve attendee information for any attendee in the Concur company, regardless of whether they are Private or Shared. In future releases, this resource will be enhanced to provide full attendee management functionality.
 
 This API allows developers to manage attendees in Concur. The Attendee resource can be used to retrieve attendee information for private or shared attendees. In future releases, the Attendee resource will be updated with additional functionality for managing all attendees in Concur.
diff --git a/src/api-reference/expense/expense-report/expense-report-get.markdown b/src/api-reference/expense/expense-report/expense-report-get.markdown
index 3cd296543c..81a7ea37a4 100644
--- a/src/api-reference/expense/expense-report/expense-report-get.markdown
+++ b/src/api-reference/expense/expense-report/expense-report-get.markdown
@@ -1,12 +1,14 @@
----
+---
 title: Get report details
 layout: reference
 ---
 
 # Get Report Details
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 **NOTE:** Find the newer version 3.0 [here.](/api-reference/expense/expense-report/v3.reports.html#retrieve-a-report-by-id-)  
 
 
diff --git a/src/api-reference/expense/expense-report/v1dot1.expense-group-configurations.markdown b/src/api-reference/expense/expense-report/v1dot1.expense-group-configurations.markdown
index bacf650339..a57c54132b 100644
--- a/src/api-reference/expense/expense-report/v1dot1.expense-group-configurations.markdown
+++ b/src/api-reference/expense/expense-report/v1dot1.expense-group-configurations.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Expense Group Configurations v1.1
 layout: reference
 
@@ -8,9 +8,11 @@ redirect_from:
 ---
 
 # Expense Group Configurations v1.1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 The Expense Group Configuration contains the list of Expense Polices, Expense Types and Payment Types for the Expense Group the user specified in the OAuth access token is assigned to.
 
 ## Limitations
diff --git a/src/api-reference/expense/expense-report/v1dot1.expense-itemization.markdown b/src/api-reference/expense/expense-report/v1dot1.expense-itemization.markdown
index 9adc98a15f..cb610c6006 100644
--- a/src/api-reference/expense/expense-report/v1dot1.expense-itemization.markdown
+++ b/src/api-reference/expense/expense-report/v1dot1.expense-itemization.markdown
@@ -9,7 +9,13 @@ redirect_from:
 
 # Expense Entry Itemization v1.1
 
-{% include deprecation-alert.html deprecation_date="05/19/2016" unsupported_date="11/19/2016" content=deprecation_content %}
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Deprecation Date: 05/19/2016</p>
+  <p>Unsupported Date: 11/19/2016</p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 
 Expense Entry Itemizations are children of an expense entry that subdivide the expense. A common use case for itemizations is on a hotel bill, which can have separate itemizations for room rate, room tax, and services such as laundry or minibar.
 
diff --git a/src/api-reference/expense/expense-report/v1dot1.report-full-details.markdown b/src/api-reference/expense/expense-report/v1dot1.report-full-details.markdown
index e03b1f853b..9c542e9b4b 100644
--- a/src/api-reference/expense/expense-report/v1dot1.report-full-details.markdown
+++ b/src/api-reference/expense/expense-report/v1dot1.report-full-details.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Report Full Details v1.1
 layout: reference
 
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # Report Full Details v1.1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 Retrieves the full set of information for the report. Includes the Report Header, Entry, Attendee, Itemization and Allocation details.
 
 ## Limitations
diff --git a/src/api-reference/expense/expense-report/v1dot1.reports-list.markdown b/src/api-reference/expense/expense-report/v1dot1.reports-list.markdown
index 46fbca893c..3331a7dcdd 100644
--- a/src/api-reference/expense/expense-report/v1dot1.reports-list.markdown
+++ b/src/api-reference/expense/expense-report/v1dot1.reports-list.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Expense Reports List v1.1
 layout: reference
 
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # Expense Reports List v1.1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 ## Get list of expense reports
 
 Retrieves a list of reports. This endpoint can be used to view reports for one user, or to view recent reports for the entire company. If you get reports for one user, you can view reports owned by the user specified in the OAuth access token. If you choose to get all the reports for the company, you must use the LastModified date query string to view reports for a 24 hour period. You can provide an optional View to target search results. If no view or date string is provided, the web service will return all Recent reports for the specified user. If the `LastModified` query string is provided, the results do not filter based on the specified user. This endpoint can support frequent requests, where the developer tracks the previous date/time that the endpoint was called, and uses that as the date/time for the next request.
diff --git a/src/api-reference/expense/expense-report/v1dot1.reports.markdown b/src/api-reference/expense/expense-report/v1dot1.reports.markdown
index 85fb52f7b5..11072250b8 100644
--- a/src/api-reference/expense/expense-report/v1dot1.reports.markdown
+++ b/src/api-reference/expense/expense-report/v1dot1.reports.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Expense Report Header v1.1
 layout: reference
 
@@ -8,9 +8,11 @@ redirect_from:
 ---
 
 # Expense Report Header v1.1
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 **NOTE:** Find the newer version 3.0 [here.](/api-reference/expense/expense-report/v3.reports.html)
 
 The expense report header contains classification information for the expense report, and serves as the container for the expense entries.
diff --git a/src/api-reference/expense/expense-report/v2.expense-entry-attendee.markdown b/src/api-reference/expense/expense-report/v2.expense-entry-attendee.markdown
index 99d2110f77..fe55b49c21 100644
--- a/src/api-reference/expense/expense-report/v2.expense-entry-attendee.markdown
+++ b/src/api-reference/expense/expense-report/v2.expense-entry-attendee.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Expense Entry Attendee v2
 layout: reference
 
@@ -9,9 +9,11 @@ redirect_from:
 ---
 
 # Expense Entry Attendee v2
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 **NOTE:** Find the newer version 3.0 [here.](./v3.expense-entry-attendee.html)
 
 The Expense Entry Attendees manages the relationship between the attendees and the expense report and entry, for the specified expense entry. This resource does not include the full attendee information, which can be accessed using the Get Attendees function.
diff --git a/src/api-reference/expense/expense-report/v2.reports.markdown b/src/api-reference/expense/expense-report/v2.reports.markdown
index d38e8badcd..577a45315b 100644
--- a/src/api-reference/expense/expense-report/v2.reports.markdown
+++ b/src/api-reference/expense/expense-report/v2.reports.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Reports v2
 layout: reference
 
@@ -8,9 +8,11 @@ redirect_from:
 ---
 
 # Reports v2
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 **NOTE:** Find the newer version 3.0 [here.](/api-reference/expense/expense-report/v3.reports.html)  
 
 The expense reports in Concur.
diff --git a/src/api-reference/receipts/v3.receipts.markdown b/src/api-reference/receipts/v3.receipts.markdown
index 08fff49cac..16f83849b6 100644
--- a/src/api-reference/receipts/v3.receipts.markdown
+++ b/src/api-reference/receipts/v3.receipts.markdown
@@ -1,15 +1,16 @@
----
+---
 title: Receipts v3 (Deprecated)
 layout: reference
 ---
 
-{% capture deprecation_content %}
-
-[Receipts v4](./get-started.html) which replaces this API opens doors to global availability, enriched schemas, and better support for detailed tax content.
-
-{% endcapture %}
-
-{% include deprecation-alert.html deprecation_date="02/07/2017" unsupported_date="08/07/2017" content=deprecation_content %}
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Deprecation Date: 02/07/2017</p>
+  <p>Unsupported Date: 08/07/2017</p>
+  <p>[Receipts v4](./get-started.html) which replaces this API opens doors to global availability, enriched schemas, and better support for detailed tax content.</p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 
 ---
 
diff --git a/src/api-reference/request/v1.request.markdown b/src/api-reference/request/v1.request.markdown
index cba900f131..38dbc13fb7 100644
--- a/src/api-reference/request/v1.request.markdown
+++ b/src/api-reference/request/v1.request.markdown
@@ -1,13 +1,15 @@
----
+---
 title: Travel Request v1
 layout: reference
 ---
 # Travel Request v1
 
 **Decommissioned as of May 2023.**
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 Concur Travel Request is designed to help businesses control expenses by requiring employees to obtain approval before incurring expenses. The Travel Request resource provides the ability to view requests and update the workflow for travel requests.
 
 Requests version 1.0 retrieves a list of up to 1000 travel requests. The request can include one or multiple search terms. This resource supports the following operations:
diff --git a/src/api-reference/travel-profile/v1.notification-company-resource.markdown b/src/api-reference/travel-profile/v1.notification-company-resource.markdown
index 542351c70d..edcb1df269 100644
--- a/src/api-reference/travel-profile/v1.notification-company-resource.markdown
+++ b/src/api-reference/travel-profile/v1.notification-company-resource.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Travel Profile v1 - Company Notification
 layout: reference
 
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # Travel Profile v1 - Company Notification
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 A subscription to a notification when any user in the SAP Concur company changes the specified features of their SAP Concur account or data. Currently supports notifications for the following events: Itinerary change (create or update), Travel Profile basic information change.
 
 This functionality requires that the partner complete the OAuth process with an administrative user from the SAP Concur company. This resource can only be accessed by partner applications that have selected the User API scope.
diff --git a/src/api-reference/travel-profile/v1.notification-user-resource.markdown b/src/api-reference/travel-profile/v1.notification-user-resource.markdown
index 30c9c22966..04e0b3decf 100644
--- a/src/api-reference/travel-profile/v1.notification-user-resource.markdown
+++ b/src/api-reference/travel-profile/v1.notification-user-resource.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Travel Profile v1 - User Notification
 layout: reference
 
@@ -7,9 +7,11 @@ redirect_from:
 ---
 
 # Travel Profile v1 - User Notification
-
-{% include deprecation-alert.html %}
-
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 A subscription to a notification when the SAP Concur user changes the specified features of their SAP Concur account or data. Currently supports notifications for the following events: Itinerary change (create or update), Travel Profile basic information change, or Travel Profile Form of Payment change. This functionality is restricted to Travel Suppliers or TMCs (Travel Management Companies) who have registered with SAP Concur.
 
 **NOTE**: This resource can only be accessed by partner applications that have selected the `User` API scope.
diff --git a/src/api-reference/travel-profile/v1.profile-resource.markdown b/src/api-reference/travel-profile/v1.profile-resource.markdown
index 2be2e4d95d..4a905b7975 100644
--- a/src/api-reference/travel-profile/v1.profile-resource.markdown
+++ b/src/api-reference/travel-profile/v1.profile-resource.markdown
@@ -1,4 +1,4 @@
----
+---
 title: Travel Profile Resource v1
 layout: reference
 
@@ -8,7 +8,12 @@ redirect_from:
 
 # Travel Profile Resource v1
 
-{% include deprecation-alert.html deprecation_date="04/01/2016" %}
+<div class="alert alert-danger">
+  <p><strong>This API has been deprecated.</strong></p>
+  <p>Deprecation Date: 04/01/2016</p>
+  <p>Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.</p>
+  <p>Learn more in the <a href="/tools-support/deprecation-policy.html">API Lifecycle &amp; Deprecation Policy.</a></p>
+</div>
 
 Current version: [Travel Profile v2](./v2.profile-resource.html)
 
diff --git a/src/tools-support/release-notes/api/2025-01-09.md b/src/tools-support/release-notes/api/2025-01-09.md
index 230dd8fa55..96eb2ba48f 100644
--- a/src/tools-support/release-notes/api/2025-01-09.md
+++ b/src/tools-support/release-notes/api/2025-01-09.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, January 2025
 layout: reference
 ---
@@ -184,8 +184,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Preview
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -193,7 +193,7 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
diff --git a/src/tools-support/release-notes/api/2025-02-06.md b/src/tools-support/release-notes/api/2025-02-06.md
index 6db9382d94..6704d2431b 100644
--- a/src/tools-support/release-notes/api/2025-02-06.md
+++ b/src/tools-support/release-notes/api/2025-02-06.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, February 2025
 layout: reference
 ---
@@ -123,8 +123,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Preview
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -132,7 +132,7 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
diff --git a/src/tools-support/release-notes/api/2025-03-06.md b/src/tools-support/release-notes/api/2025-03-06.md
index 8c6b3b45a2..a50978fef3 100644
--- a/src/tools-support/release-notes/api/2025-03-06.md
+++ b/src/tools-support/release-notes/api/2025-03-06.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, March 2025
 layout: reference
 ---
@@ -157,8 +157,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Preview
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -166,7 +166,7 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-04-03.md b/src/tools-support/release-notes/api/2025-04-03.md
index e05102ff79..8ee221b2f5 100644
--- a/src/tools-support/release-notes/api/2025-04-03.md
+++ b/src/tools-support/release-notes/api/2025-04-03.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, April 2025
 layout: reference
 ---
@@ -108,8 +108,8 @@ Date|API|Preview
 ---|---|---
 [03/2025](/tools-support/release-notes/api/2025-03-06.html)|Cash Advance Associations v4 APIs for Reports|The Expense Report Service API suite will be updated to include APIs to retrieve, update, and delete cash advance associations to a report.
 [03/2025](/tools-support/release-notes/api/2025-03-06.html)|Support of Hotel Date Modification for Hotel Connectors|Hotel connectors will support the modification of check-in and check-out dates using the Hotel Service v4 Modify endpoint. This will allow users to change their dates of stay without having to cancel and rebook.
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -117,7 +117,7 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-05-05.md b/src/tools-support/release-notes/api/2025-05-05.md
index 76e36aca04..6694c3c537 100644
--- a/src/tools-support/release-notes/api/2025-05-05.md
+++ b/src/tools-support/release-notes/api/2025-05-05.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, May 2025
 layout: reference
 ---
@@ -79,8 +79,8 @@ Date|API|Preview
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Expense v4 DELETE APIs for Reports v4 and Expenses v4|The Expense Report Service API suite will be updated to include APIs to delete unsubmitted reports and expenses.
 [03/2025](/tools-support/release-notes/api/2025-03-06.html)|Support of Hotel Date Modification for Hotel Connectors|Hotel connectors will support the modification of check-in and check-out dates using the Hotel Service v4 Modify endpoint. This will allow users to change their dates of stay without having to cancel and rebook.
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -89,7 +89,7 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 Date|API|Details
 ---|---|---
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-06-04.md b/src/tools-support/release-notes/api/2025-06-04.md
index 675f789635..ce7c7d3342 100644
--- a/src/tools-support/release-notes/api/2025-06-04.md
+++ b/src/tools-support/release-notes/api/2025-06-04.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, June 2025
 layout: reference
 ---
@@ -146,8 +146,8 @@ Date|API|Preview
 ---|---|---
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
 [03/2025](/tools-support/release-notes/api/2025-03-06.html)|Support of Hotel Date Modification for Hotel Connectors|Hotel connectors will support the modification of check-in and check-out dates using the Hotel Service v4 Modify endpoint. This will allow users to change their dates of stay without having to cancel and rebook.
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -156,7 +156,7 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 Date|API|Details
 ---|---|---
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-07-10.md b/src/tools-support/release-notes/api/2025-07-10.md
index 0140448f41..ccfb4096ea 100644
--- a/src/tools-support/release-notes/api/2025-07-10.md
+++ b/src/tools-support/release-notes/api/2025-07-10.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, July 2025
 layout: reference
 ---
@@ -123,8 +123,8 @@ Date|API|Preview
 [06/2025](/tools-support/release-notes/api/2025-06-04.html)|Detokenizer (DTK) v5 API|The FIPS Compliant v5 Credit Card Detokenization API will be set to launch within the CCPS environment for IBCP customers. This compliance-driven initiative aligns with the Federal Information Processor Standards (FIPS) to ensure robust protection of sensitive data, per U.S. federal requirements.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
 [03/2025](/tools-support/release-notes/api/2025-03-06.html)|Support of Hotel Date Modification for Hotel Connectors|Hotel connectors will support the modification of check-in and check-out dates using the Hotel Service v4 Modify endpoint. This will allow users to change their dates of stay without having to cancel and rebook.
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -133,7 +133,7 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 Date|API|Details
 ---|---|---
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-08-07.md b/src/tools-support/release-notes/api/2025-08-07.md
index 3b08e9e795..928a6611bd 100644
--- a/src/tools-support/release-notes/api/2025-08-07.md
+++ b/src/tools-support/release-notes/api/2025-08-07.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, August 2025
 layout: reference
 ---
@@ -100,8 +100,8 @@ Date|API|Preview
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Support for IPv6|The SAP Concur platform will support IPv6 for network communication to and from SAP Concur solutions. This implementation is expected for Q4/2025. Previously, IPv6 was only supported for inbound HTTPS calls, and all other inbound and outbound calls supported only IPv4. 
 [06/2025](/tools-support/release-notes/api/2025-06-04.html)|Detokenizer (DTK) v5 API|The FIPS Compliant v5 Credit Card Detokenization API will be set to launch within the CCPS environment for IBCP customers. This compliance-driven initiative aligns with the Federal Information Processor Standards (FIPS) to ensure robust protection of sensitive data, per U.S. federal requirements.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -114,7 +114,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-09-04.md b/src/tools-support/release-notes/api/2025-09-04.md
index 267acaee3f..db85e63a5f 100644
--- a/src/tools-support/release-notes/api/2025-09-04.md
+++ b/src/tools-support/release-notes/api/2025-09-04.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, September 2025
 layout: reference
 ---
@@ -143,8 +143,8 @@ Date|API|Preview
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Support for IPv6|The SAP Concur platform will support IPv6 for network communication to and from SAP Concur solutions. This implementation is expected for Q4/2025. Previously, IPv6 was only supported for inbound HTTPS calls, and all other inbound and outbound calls supported only IPv4. 
 [06/2025](/tools-support/release-notes/api/2025-06-04.html)|Detokenizer (DTK) v5 API|The FIPS Compliant v5 Credit Card Detokenization API will be set to launch within the CCPS environment for IBCP customers. This compliance-driven initiative aligns with the Federal Information Processor Standards (FIPS) to ensure robust protection of sensitive data, per U.S. federal requirements.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -157,7 +157,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-10-02.md b/src/tools-support/release-notes/api/2025-10-02.md
index 7ad80784ad..f69bde202f 100644
--- a/src/tools-support/release-notes/api/2025-10-02.md
+++ b/src/tools-support/release-notes/api/2025-10-02.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, October 2025
 layout: reference
 ---
@@ -201,8 +201,8 @@ Date|API|Preview
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Support for IPv6|The SAP Concur platform will support IPv6 for network communication to and from SAP Concur solutions. This implementation is expected for Q4/2025. Previously, IPv6 was only supported for inbound HTTPS calls, and all other inbound and outbound calls supported only IPv4. 
 [06/2025](/tools-support/release-notes/api/2025-06-04.html)|Detokenizer (DTK) v5 API|The FIPS Compliant v5 Credit Card Detokenization API will be set to launch within the CCPS environment for IBCP customers. This compliance-driven initiative aligns with the Federal Information Processor Standards (FIPS) to ensure robust protection of sensitive data, per U.S. federal requirements.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -215,7 +215,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-11-11.md b/src/tools-support/release-notes/api/2025-11-11.md
index 1d08b6ced1..f9cd44697e 100644
--- a/src/tools-support/release-notes/api/2025-11-11.md
+++ b/src/tools-support/release-notes/api/2025-11-11.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, November 2025
 layout: reference
 ---
@@ -174,8 +174,8 @@ Date|API|Preview
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Support for IPv6|The SAP Concur platform will support IPv6 for network communication to and from SAP Concur solutions. This implementation is expected for Q4/2025. Previously, IPv6 was only supported for inbound HTTPS calls, and all other inbound and outbound calls supported only IPv4. 
 [06/2025](/tools-support/release-notes/api/2025-06-04.html)|Detokenizer (DTK) v5 API|The FIPS Compliant v5 Credit Card Detokenization API will be set to launch within the CCPS environment for IBCP customers. This compliance-driven initiative aligns with the Federal Information Processor Standards (FIPS) to ensure robust protection of sensitive data, per U.S. federal requirements.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -189,7 +189,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2025-12-04.md b/src/tools-support/release-notes/api/2025-12-04.md
index 603d756389..17e73ef55a 100644
--- a/src/tools-support/release-notes/api/2025-12-04.md
+++ b/src/tools-support/release-notes/api/2025-12-04.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, December 2025
 layout: reference
 ---
@@ -213,8 +213,8 @@ Date|API|Preview
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|New Attributes for Spend User v4.1|The Spend User v4.1 API will allow you to access the `processorReportAccess` field in the User Preference extension and the User extension will allow you to access the following fields: `officeLocationCountry`, `officeLocationStateProvince`, `officeLocationCity`.
 [06/2025](/tools-support/release-notes/api/2025-06-04.html)|Detokenizer (DTK) v5 API|The FIPS Compliant v5 Credit Card Detokenization API will be set to launch within the CCPS environment for IBCP customers. This compliance-driven initiative aligns with the Federal Information Processor Standards (FIPS) to ensure robust protection of sensitive data, per U.S. federal requirements.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -228,7 +228,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2026-01-12.md b/src/tools-support/release-notes/api/2026-01-12.md
index 84c3b4352e..e5ca375d65 100644
--- a/src/tools-support/release-notes/api/2026-01-12.md
+++ b/src/tools-support/release-notes/api/2026-01-12.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, January 2026
 layout: reference
 ---
@@ -268,8 +268,8 @@ Date|API|Preview
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|New Attributes for Spend User v4.1|The Spend User v4.1 API will allow you to access the `processorReportAccess` field in the User Preference extension and the User extension will allow you to access the following fields: `officeLocationCountry`, `officeLocationStateProvince`, `officeLocationCity`.
 [06/2025](/tools-support/release-notes/api/2025-06-04.html)|Detokenizer (DTK) v5 API|The FIPS Compliant v5 Credit Card Detokenization API will be set to launch within the CCPS environment for IBCP customers. This compliance-driven initiative aligns with the Federal Information Processor Standards (FIPS) to ensure robust protection of sensitive data, per U.S. federal requirements.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|New Fields Added to Financial Integration Services (FIS) v4 API|For customers of the Concur Expense Professional Edition using the Financial Integration Services (FIS) v4 API, additional fields will be included in the Expense report document payload and mileage fields will be added to the payroll document schema. 
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -283,7 +283,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2026-02-04.md b/src/tools-support/release-notes/api/2026-02-04.md
index dd238f5e2a..dacee46f73 100644
--- a/src/tools-support/release-notes/api/2026-02-04.md
+++ b/src/tools-support/release-notes/api/2026-02-04.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, February 2026
 layout: reference
 ---
@@ -103,7 +103,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2026-03-03.md b/src/tools-support/release-notes/api/2026-03-03.md
index 7b3fe9b7c2..1c1b0df4fb 100644
--- a/src/tools-support/release-notes/api/2026-03-03.md
+++ b/src/tools-support/release-notes/api/2026-03-03.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, March 2026
 layout: reference
 ---
@@ -208,7 +208,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/2026-04-06.md b/src/tools-support/release-notes/api/2026-04-06.md
index 327f9b0701..57f72e7258 100644
--- a/src/tools-support/release-notes/api/2026-04-06.md
+++ b/src/tools-support/release-notes/api/2026-04-06.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, April 2026
 layout: reference
 ---
@@ -174,7 +174,7 @@ Date|API|Details
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendees v3 API|Effective July 1, 2025, the Attendees v3 API was deprecated. This has been replaced by Attendees v4. Decommission will follow.
 [07/2025](/tools-support/release-notes/api/2025-07-10.html)|Deprecation of Attendee Types v3 API|Effective July 1, 2025, the Attendee Types v3 API was deprecated. This has been replaced by Attendee Types v4. Decommission will follow.
 [04/2025](/tools-support/release-notes/api/2025-04-03.html)|Deprecation of Attendees v1, v1.1, and v2|Effective October 9, 2018, we have deprecated the Attendees v1, v1.1, and v2 APIs. Decommission will follow.
-[03/2024](/tools-support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
 [06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
 [01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
diff --git a/src/tools-support/release-notes/api/archive/2021-09-17.md b/src/tools-support/release-notes/api/archive/2021-09-17.md
index b56adc570e..5ce4f6f816 100644
--- a/src/tools-support/release-notes/api/archive/2021-09-17.md
+++ b/src/tools-support/release-notes/api/archive/2021-09-17.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, September 2021
 layout: reference
 ---
@@ -355,7 +355,7 @@ This feature is automatically available; there are no additional configuration o
 
 ## <a name="cash-advance-v4"></a>Cash Advance v4 API Available
 
-The [Cash Advance v4](/api-reference/cash-advance/v4.cash-advance.html) API will empower an employee to request and receive cash in advance of a trip. Cash Advance v4 will ensure that a user is not out of cash during a business trip. In markets where corporate cards are seldom issued, Cash Advance v4 will provide a useful mechanism to ensure the employee is not out of pocket.
+The [Cash Advance v4](/api-reference/cash-advance/v4-1.cash-advance.html) API will empower an employee to request and receive cash in advance of a trip. Cash Advance v4 will ensure that a user is not out of cash during a business trip. In markets where corporate cards are seldom issued, Cash Advance v4 will provide a useful mechanism to ensure the employee is not out of pocket.
 
 ### Business Purpose / Client Benefit
 
diff --git a/src/tools-support/release-notes/api/archive/2021-10-15.md b/src/tools-support/release-notes/api/archive/2021-10-15.md
index 0c916826d6..df757fdcbf 100644
--- a/src/tools-support/release-notes/api/archive/2021-10-15.md
+++ b/src/tools-support/release-notes/api/archive/2021-10-15.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, October 2021
 layout: reference
 ---
@@ -80,22 +80,22 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-hotel-v1)|Decommission of Hotel Service v1|Following the deprecation of Hotel Service v1 APIs in March 2019, we will be decommissioning the Hotel Service v1 APIs on December 31, 2021. Any configuration that uses hotel content connectors that rely on HSv1 will be affected. Please reference the Hotel Service Travel Service Guide for a list of connectors. If you are a client of one of these connectors, please work with your TMC or administrator to switch to an HSv2 connection and/or GDS for your hotel content needs.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-hotel-v1)|Decommission of Hotel Service v1|Following the deprecation of Hotel Service v1 APIs in March 2019, we will be decommissioning the Hotel Service v1 APIs on December 31, 2021. Any configuration that uses hotel content connectors that rely on HSv1 will be affected. Please reference the Hotel Service Travel Service Guide for a list of connectors. If you are a client of one of these connectors, please work with your TMC or administrator to switch to an HSv2 connection and/or GDS for your hotel content needs.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-list-item)|Request v4 - Link to List Item Endpoint|In October 2021, we will be introducing a new link toward the List Item endpoint for Request custom fields related to a List. The List Item API will enable Request consumers to have a better interaction with custom fields related to a List (create/update custom fields related to a List). To enable a better interaction between Concur APIs, a new link will be provided within the Request `customField` schema to redirect to the corresponding List Item endpoint of the List API.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Effective October, 1st 2021, Concur Request will deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Effective beginning of November 2021, the Request Cash Advance List endpoint will redirect consumers to the Retrieve a Cash Advance endpoint, part of the Cash Advance v4 API.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-endpoint)|Request v4 - Agency Proposal Endpoint|In Q4 2021, we will release an additional Request v4 API endpoint that will offer the ability for travel agencies to interact with Concur Request to submit travel itineraries directly into a request, via the agency proposal feature with Request v4 API.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-list-item)|Request v4 - Link to List Item Endpoint|In October 2021, we will be introducing a new link toward the List Item endpoint for Request custom fields related to a List. The List Item API will enable Request consumers to have a better interaction with custom fields related to a List (create/update custom fields related to a List). To enable a better interaction between Concur APIs, a new link will be provided within the Request `customField` schema to redirect to the corresponding List Item endpoint of the List API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Effective October, 1st 2021, Concur Request will deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Effective beginning of November 2021, the Request Cash Advance List endpoint will redirect consumers to the Retrieve a Cash Advance endpoint, part of the Cash Advance v4 API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-endpoint)|Request v4 - Agency Proposal Endpoint|In Q4 2021, we will release an additional Request v4 API endpoint that will offer the ability for travel agencies to interact with Concur Request to submit travel itineraries directly into a request, via the agency proposal feature with Request v4 API.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2021-11-10.md b/src/tools-support/release-notes/api/archive/2021-11-10.md
index 69420aa725..0c74646c72 100644
--- a/src/tools-support/release-notes/api/archive/2021-11-10.md
+++ b/src/tools-support/release-notes/api/archive/2021-11-10.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, November 2021
 layout: reference
 ---
@@ -96,23 +96,23 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-hotel-v1)|Decommission of Hotel Service v1|Following the deprecation of Hotel Service v1 APIs in March 2019, we will be decommissioning the Hotel Service v1 APIs on December 31, 2021. Any configuration that uses hotel content connectors that rely on HSv1 will be affected. Please reference the Hotel Service Travel Service Guide for a list of connectors. If you are a client of one of these connectors, please work with your TMC or administrator to switch to an HSv2 connection and/or GDS for your hotel content needs.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-hotel-v1)|Decommission of Hotel Service v1|Following the deprecation of Hotel Service v1 APIs in March 2019, we will be decommissioning the Hotel Service v1 APIs on December 31, 2021. Any configuration that uses hotel content connectors that rely on HSv1 will be affected. Please reference the Hotel Service Travel Service Guide for a list of connectors. If you are a client of one of these connectors, please work with your TMC or administrator to switch to an HSv2 connection and/or GDS for your hotel content needs.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-list-item)|Request v4 - Link to List Item Endpoint|In October 2021, we will be introducing a new link toward the List Item endpoint for Request custom fields related to a List. The List Item API will enable Request consumers to have a better interaction with custom fields related to a List (create/update custom fields related to a List). To enable a better interaction between Concur APIs, a new link will be provided within the Request `customField` schema to redirect to the corresponding List Item endpoint of the List API.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Effective October, 1st 2021, Concur Request will deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Effective beginning of November 2021, the Request Cash Advance List endpoint will redirect consumers to the Retrieve a Cash Advance endpoint, part of the Cash Advance v4 API.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-endpoint)|Request v4 - Agency Proposal Endpoint|In Q4 2021, we will release an additional Request v4 API endpoint that will offer the ability for travel agencies to interact with Concur Request to submit travel itineraries directly into a request, via the agency proposal feature with Request v4 API.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-list-item)|Request v4 - Link to List Item Endpoint|In October 2021, we will be introducing a new link toward the List Item endpoint for Request custom fields related to a List. The List Item API will enable Request consumers to have a better interaction with custom fields related to a List (create/update custom fields related to a List). To enable a better interaction between Concur APIs, a new link will be provided within the Request `customField` schema to redirect to the corresponding List Item endpoint of the List API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Effective October, 1st 2021, Concur Request will deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Effective beginning of November 2021, the Request Cash Advance List endpoint will redirect consumers to the Retrieve a Cash Advance endpoint, part of the Cash Advance v4 API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-endpoint)|Request v4 - Agency Proposal Endpoint|In Q4 2021, we will release an additional Request v4 API endpoint that will offer the ability for travel agencies to interact with Concur Request to submit travel itineraries directly into a request, via the agency proposal feature with Request v4 API.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2021-12-09.md b/src/tools-support/release-notes/api/archive/2021-12-09.md
index ec15f3d1f1..7f59fe5cad 100644
--- a/src/tools-support/release-notes/api/archive/2021-12-09.md
+++ b/src/tools-support/release-notes/api/archive/2021-12-09.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, December 2021
 layout: reference
 ---
@@ -63,24 +63,24 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-hotel-v1)|Decommission of Hotel Service v1|Following the deprecation of Hotel Service v1 APIs in March 2019, we will be decommissioning the Hotel Service v1 APIs on December 31, 2021. Any configuration that uses hotel content connectors that rely on HSv1 will be affected. Please reference the Hotel Service Travel Service Guide for a list of connectors. If you are a client of one of these connectors, please work with your TMC or administrator to switch to an HSv2 connection and/or GDS for your hotel content needs.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-hotel-v1)|Decommission of Hotel Service v1|Following the deprecation of Hotel Service v1 APIs in March 2019, we will be decommissioning the Hotel Service v1 APIs on December 31, 2021. Any configuration that uses hotel content connectors that rely on HSv1 will be affected. Please reference the Hotel Service Travel Service Guide for a list of connectors. If you are a client of one of these connectors, please work with your TMC or administrator to switch to an HSv2 connection and/or GDS for your hotel content needs.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[11/2021](/tools-support/release-notes/api/2021-11-10.html)|Some TLSv1.2 Ciphers No Longer Supported|Beginning on February 1, 2022, SAP Concur solutions will no longer support connections to *.concursolutions.com and * api.concursolutions.com that use certain TLSv1.2 ciphers.
-[11/2021](/tools-support/release-notes/api/2021-11-10.html)|Travel Profile v2 API Will No Longer Provide MobileName, MobileDevice, and PrimaryMobile Attribute in User Profiles|Beginning on December 15,2021, [Travel Profile v2](https://developer.concur.com/api-reference/travel-profile/v2.profile-resource.html) API will no longer return `MobileName`, `MobileDevice`, and `PrimaryMobile` attribute in User profiles.
-[11/2021](/tools-support/release-notes/api/2021-11-10.html)|Travel Profile v2 API Will No Longer Return Latitude and Longitude of the Work Address in User Profiles|Beginning on December 15, 2021, the [Travel Profile v2](https://developer.concur.com/api-reference/travel-profile/v2.profile-resource.html) API will no longer return the Work Address `Latitude` and `Longitude` fields in User profiles.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[11/2021](/tools-support/release-notes/api/archive/2021-11-10.html)|Some TLSv1.2 Ciphers No Longer Supported|Beginning on February 1, 2022, SAP Concur solutions will no longer support connections to *.concursolutions.com and * api.concursolutions.com that use certain TLSv1.2 ciphers.
+[11/2021](/tools-support/release-notes/api/archive/2021-11-10.html)|Travel Profile v2 API Will No Longer Provide MobileName, MobileDevice, and PrimaryMobile Attribute in User Profiles|Beginning on December 15,2021, [Travel Profile v2](https://developer.concur.com/api-reference/travel-profile/v2.profile-resource.html) API will no longer return `MobileName`, `MobileDevice`, and `PrimaryMobile` attribute in User profiles.
+[11/2021](/tools-support/release-notes/api/archive/2021-11-10.html)|Travel Profile v2 API Will No Longer Return Latitude and Longitude of the Work Address in User Profiles|Beginning on December 15, 2021, the [Travel Profile v2](https://developer.concur.com/api-reference/travel-profile/v2.profile-resource.html) API will no longer return the Work Address `Latitude` and `Longitude` fields in User profiles.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-01-13.md b/src/tools-support/release-notes/api/archive/2022-01-13.md
index aa506d90e3..dc0fa920cd 100644
--- a/src/tools-support/release-notes/api/archive/2022-01-13.md
+++ b/src/tools-support/release-notes/api/archive/2022-01-13.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, January 2022
 layout: reference
 ---
@@ -91,21 +91,21 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[11/2021](/tools-support/release-notes/api/2021-11-10.html)|Some TLSv1.2 Ciphers No Longer Supported|Beginning on February 1, 2022, SAP Concur solutions will no longer support connections to *.concursolutions.com and * api.concursolutions.com that use certain TLSv1.2 ciphers.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[11/2021](/tools-support/release-notes/api/archive/2021-11-10.html)|Some TLSv1.2 Ciphers No Longer Supported|Beginning on February 1, 2022, SAP Concur solutions will no longer support connections to *.concursolutions.com and * api.concursolutions.com that use certain TLSv1.2 ciphers.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-02-17.md b/src/tools-support/release-notes/api/archive/2022-02-17.md
index 2fd6a14362..ad41f84a68 100644
--- a/src/tools-support/release-notes/api/archive/2022-02-17.md
+++ b/src/tools-support/release-notes/api/archive/2022-02-17.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, February 2022
 layout: reference
 ---
@@ -56,23 +56,23 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|In February, the Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|In February, the Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-03-17.md b/src/tools-support/release-notes/api/archive/2022-03-17.md
index e0af9a6366..6ac0663090 100644
--- a/src/tools-support/release-notes/api/archive/2022-03-17.md
+++ b/src/tools-support/release-notes/api/archive/2022-03-17.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, March 2022
 layout: reference
 ---
@@ -39,23 +39,23 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|In February, the Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|In February, the Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-04-08.md b/src/tools-support/release-notes/api/archive/2022-04-08.md
index 58909b7511..2f8a26e14b 100644
--- a/src/tools-support/release-notes/api/archive/2022-04-08.md
+++ b/src/tools-support/release-notes/api/archive/2022-04-08.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, April 2022
 layout: reference
 ---
@@ -59,23 +59,23 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|In February, the Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[01/2022](/tools-support/release-notes/api/2021-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|In February, the Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-05-19.md b/src/tools-support/release-notes/api/archive/2022-05-19.md
index 221b567ca6..bce24b0001 100644
--- a/src/tools-support/release-notes/api/archive/2022-05-19.md
+++ b/src/tools-support/release-notes/api/archive/2022-05-19.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, May 2022
 layout: reference
 ---
@@ -107,24 +107,24 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[04/2022](/tools-support/release-notes/api/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|In February, the Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2022](/tools-support/release-notes/api/archive/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|In February, the Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-06-24.md b/src/tools-support/release-notes/api/archive/2022-06-24.md
index 33af435e3c..78093c6b54 100644
--- a/src/tools-support/release-notes/api/archive/2022-06-24.md
+++ b/src/tools-support/release-notes/api/archive/2022-06-24.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, June 2022
 layout: reference
 ---
@@ -91,26 +91,26 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Hotel Service v4 API Available|The Hotel Service v4 API will allow Custom Hotel Source (CHS) vendors to provide hotel inventory, rates and booking related functionality to users of the new SAP Concur Online Booking Tool (Travel Evolution).
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
-[04/2022](/tools-support/release-notes/api/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Hotel Service v4 API Available|The Hotel Service v4 API will allow Custom Hotel Source (CHS) vendors to provide hotel inventory, rates and booking related functionality to users of the new SAP Concur Online Booking Tool (Travel Evolution).
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[04/2022](/tools-support/release-notes/api/archive/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-07-08.md b/src/tools-support/release-notes/api/archive/2022-07-08.md
index 3c5adf8c91..c71898cad7 100644
--- a/src/tools-support/release-notes/api/archive/2022-07-08.md
+++ b/src/tools-support/release-notes/api/archive/2022-07-08.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, July 2022
 layout: reference
 ---
@@ -49,26 +49,26 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Hotel Service v4 API Available|The Hotel Service v4 API will allow Custom Hotel Source (CHS) vendors to provide hotel inventory, rates and booking related functionality to users of the new SAP Concur Online Booking Tool (Travel Evolution).
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
-[04/2022](/tools-support/release-notes/api/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Hotel Service v4 API Available|The Hotel Service v4 API will allow Custom Hotel Source (CHS) vendors to provide hotel inventory, rates and booking related functionality to users of the new SAP Concur Online Booking Tool (Travel Evolution).
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[04/2022](/tools-support/release-notes/api/archive/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|New Client SSL Certificate for ESS webhook.api.concursolutions.com|To ensure the ongoing security of our products and services, the Event Subscription Service will be issuing a new webhook.api.concursolutions.com SSL certificate.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-08-12.md b/src/tools-support/release-notes/api/archive/2022-08-12.md
index 6fd16677ba..70f9285fb2 100644
--- a/src/tools-support/release-notes/api/archive/2022-08-12.md
+++ b/src/tools-support/release-notes/api/archive/2022-08-12.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, August 2022
 layout: reference
 ---
@@ -48,24 +48,24 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
-[04/2022](/tools-support/release-notes/api/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[04/2022](/tools-support/release-notes/api/archive/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-09-16.md b/src/tools-support/release-notes/api/archive/2022-09-16.md
index 86e23f40e9..a7dbb62ff2 100644
--- a/src/tools-support/release-notes/api/archive/2022-09-16.md
+++ b/src/tools-support/release-notes/api/archive/2022-09-16.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, September 2022
 layout: reference
 ---
@@ -61,24 +61,24 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
-[04/2022](/tools-support/release-notes/api/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[04/2022](/tools-support/release-notes/api/archive/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-10-14.md b/src/tools-support/release-notes/api/archive/2022-10-14.md
index 7a9291dde9..2f74b91e8a 100644
--- a/src/tools-support/release-notes/api/archive/2022-10-14.md
+++ b/src/tools-support/release-notes/api/archive/2022-10-14.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, October 2022
 layout: reference
 ---
@@ -80,24 +80,24 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
-[07/2021](/tools-support/release-notes/api/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#ongoing-user-v1)|Deprecation of User v1|User v1 service will be deprecated. User v1 service can be replaced with either the upcoming User Provisioning service and/or the [Identity v4](/api-reference/profile/v4.identity.html) service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc.
+[07/2021](/tools-support/release-notes/api/archive/2021-07-16.html#planned-dep-user)|User v3 API|We will be deprecating the User v3 API in a future release due to less secure authentication methods.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
-[04/2022](/tools-support/release-notes/api/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[04/2022](/tools-support/release-notes/api/archive/2022-04-08.html)|User Provisioning v4 API Available|The User Provisioning Service will allow users to create, update, and replace users. This will allow faster and increased access to user data attributes. Once a user is provisioned, the user identity will be created in Profile, Travel and Spend.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-11-10.md b/src/tools-support/release-notes/api/archive/2022-11-10.md
index 039529716d..3e0d7e8225 100644
--- a/src/tools-support/release-notes/api/archive/2022-11-10.md
+++ b/src/tools-support/release-notes/api/archive/2022-11-10.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, November 2022
 layout: reference
 ---
@@ -47,24 +47,24 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[04/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[04/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|Existing Concur Request APIs (v1.0, v3.0, v3.1)|Effective July 1, 2020, these APIs are replaced by the Concur Request v4 API. We have run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 API (not iso-compatibility) in order to have the vast majority of use cases managed in the previous versions also be managed in the Concur Request v4 API.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Addition of ECDSA Encryption and Cipher Retirement|To provide ongoing security for our products, we plan to remove support for select ciphers on February 16, 2023, at 5 PM PST. For more information, please see the **Planned Changes: Addition of ECDSA Encryption and Cipher Retirement** in the [October release notes](https://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/_client_shared_RN_all.htm).
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Addition of ECDSA Encryption and Cipher Retirement|To provide ongoing security for our products, we plan to remove support for select ciphers on February 16, 2023, at 5 PM PST. For more information, please see the **Planned Changes: Addition of ECDSA Encryption and Cipher Retirement** in the [October release notes](https://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/_client_shared_RN_all.htm).
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2022-12-02.md b/src/tools-support/release-notes/api/archive/2022-12-02.md
index f0a47b601b..e915cf21cd 100644
--- a/src/tools-support/release-notes/api/archive/2022-12-02.md
+++ b/src/tools-support/release-notes/api/archive/2022-12-02.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, December 2022
 layout: reference
 ---
@@ -63,25 +63,25 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
-[01/2021](/tools-support/release-notes/api/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
-[06/2020](/tools-support/release-notes/api/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
-[01/2020](/tools-support/release-notes/api/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
+[01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
+[06/2020](/tools-support/release-notes/api/archive/2020-06-24.html#planned-travel-profile-deprecation)|Travel Profile Notification v1 API|We are deprecating the Travel Profile Notification v1 APIs due to low usage.
+[01/2020](/tools-support/release-notes/api/archive/2020-04-17.html#ongoing-request-retirement)|List v1 API|We will be retiring the List v1 API in a future release. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API.
 
 ## Planned Changes
 
 Date|API|Planned Change
 ---|---|---
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Addition of ECDSA Encryption and Cipher Retirement|To provide ongoing security for our products, we plan to remove support for select ciphers on February 16, 2023, at 5 PM PST. For more information, please see the **Planned Changes: Addition of ECDSA Encryption and Cipher Retirement** in the [October release notes](https://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/_client_shared_RN_all.htm).
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
-[01/2022](/tools-support/release-notes/api/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
-[10/2021](/tools-support/release-notes/api/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
-[09/2021](/tools-support/release-notes/api/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
-[04/2021](/tools-support/release-notes/api/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Addition of ECDSA Encryption and Cipher Retirement|To provide ongoing security for our products, we plan to remove support for select ciphers on February 16, 2023, at 5 PM PST. For more information, please see the **Planned Changes: Addition of ECDSA Encryption and Cipher Retirement** in the [October release notes](https://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/_client_shared_RN_all.htm).
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|Account Termination Date Will be in UTC for Travel Profile v2|The Account Termination Date will be returned in UTC. This will provide a consistent time and date reference for all users and all data centers.
+[01/2022](/tools-support/release-notes/api/archive/2022-01-13.html)|UUID is Returned in Success Response When New User Created via Travel Profile v2 API|Travel Profile v2 will return the user’s UUID synchronously in the success response. This will allow external systems that sync data with the API to have a unique identifier for the user’s profile immediately and use it on subsequent calls to update the user’s profile.
+[10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
+[09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-parameter)|Invoice Pay v4 GET Call Parameter|GET calls will have the option to use the new `invoiceId` parameter to retrieve payment information and the ERP Document ID associated to the invoice. The feature will be automatically available; there will be no additional configuration or activation steps.
+[04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-invoice-v4-patch)|Invoice Pay v4 PATCH Endpoint|With the new PATCH, the invoice will be updated with the `erpDocumentNumber` value in the body whenever an `invoiceId` is passed as part of the API URL. The feature will be automatically available; there will be no additional configuration or activation steps.
diff --git a/src/tools-support/release-notes/api/archive/2023-01-05.md b/src/tools-support/release-notes/api/archive/2023-01-05.md
index 6db3011f8b..1854641872 100644
--- a/src/tools-support/release-notes/api/archive/2023-01-05.md
+++ b/src/tools-support/release-notes/api/archive/2023-01-05.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, January 2023
 layout: reference
 ---
@@ -67,12 +67,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation of Request APIs (v1.0, v3.0 and v3.1)|Effective March 1st, 2020, the Request APIs (v1.0, v3.0 and v3.1) have been deprecated. They have been replaced by [Request v4](/api-reference/request/v4.get-started.html). Decommission will follow on May 31st, 2023.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Once Vendors v3.1 is released, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation of Request APIs (v1.0, v3.0 and v3.1)|Effective March 1st, 2020, the Request APIs (v1.0, v3.0 and v3.1) have been deprecated. They have been replaced by [Request v4](/api-reference/request/v4.get-started.html). Decommission will follow on May 31st, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Once Vendors v3.1 is released, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -83,7 +83,7 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Addition of ECDSA Encryption and Cipher Retirement|To provide ongoing security for our products, we plan to remove support for select ciphers on February 16, 2023, at 5 PM PST. For more information, please see the **Planned Changes: Addition of ECDSA Encryption and Cipher Retirement** in the [October release notes](https://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/_client_shared_RN_all.htm).
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Addition of ECDSA Encryption and Cipher Retirement|To provide ongoing security for our products, we plan to remove support for select ciphers on February 16, 2023, at 5 PM PST. For more information, please see the **Planned Changes: Addition of ECDSA Encryption and Cipher Retirement** in the [October release notes](https://www.concurtraining.com/customers/tech_pubs/RN_shared_planned/_client_shared_RN_all.htm).
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
 [10/2021](/tools-support/release-notes/api/archive/2021-10-15.html)|Report Details v2 API Vulnerability Patch|We will be adding additional security to the Report Details v2 API. Current callers may receive a `401 - Unauthorized` response if using an unauthorized admin OAuth token to access reports.
 [09/2021](/tools-support/release-notes/api/archive/2021-09-17.html#planned-request-cash-advance)|Request v4 - Deprecation of the Request Cash Advance Endpoint|Initially planned for October 2021, Concur Request will soon deprecate the [Request Cash Advance detail endpoint](https://developer.concur.com/api-reference/request/v4.endpoints.cashadvance-resources.html). Date will be communicated in future communications.
diff --git a/src/tools-support/release-notes/api/archive/2023-02-03.md b/src/tools-support/release-notes/api/archive/2023-02-03.md
index 9edca436d4..25b9d7148b 100644
--- a/src/tools-support/release-notes/api/archive/2023-02-03.md
+++ b/src/tools-support/release-notes/api/archive/2023-02-03.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, February 2023
 layout: reference
 ---
@@ -85,12 +85,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation of Request APIs (v1.0, v3.0 and v3.1)|Effective March 1st, 2020, the Request APIs (v1.0, v3.0 and v3.1) have been deprecated. They have been replaced by [Request v4](/api-reference/request/v4.get-started.html). Decommission will follow on May 31st, 2023.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation of Request APIs (v1.0, v3.0 and v3.1)|Effective March 1st, 2020, the Request APIs (v1.0, v3.0 and v3.1) have been deprecated. They have been replaced by [Request v4](/api-reference/request/v4.get-started.html). Decommission will follow on May 31st, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -101,4 +101,4 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
diff --git a/src/tools-support/release-notes/api/archive/2023-03-10.md b/src/tools-support/release-notes/api/archive/2023-03-10.md
index 18cf600309..3d8facf439 100644
--- a/src/tools-support/release-notes/api/archive/2023-03-10.md
+++ b/src/tools-support/release-notes/api/archive/2023-03-10.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, March 2023
 layout: reference
 ---
@@ -50,12 +50,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation of Request APIs (v1.0, v3.0 and v3.1)|Effective March 1st, 2020, the Request APIs (v1.0, v3.0 and v3.1) have been deprecated. They have been replaced by [Request v4](/api-reference/request/v4.get-started.html). Decommission will follow on May 31st, 2023.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation of Request APIs (v1.0, v3.0 and v3.1)|Effective March 1st, 2020, the Request APIs (v1.0, v3.0 and v3.1) have been deprecated. They have been replaced by [Request v4](/api-reference/request/v4.get-started.html). Decommission will follow on May 31st, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -66,5 +66,5 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
-[05/2022](/tools-support/release-notes/api/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[05/2022](/tools-support/release-notes/api/archive/2022-05-19.html)|Filters for Identity v4 API|We will be releasing SCIM formatted search filters for the Identity v4 API based on user attributes to help refine search results. This functionality will allow users to use attributes, logical operators, and grouping operators to improve search results to their specific requirements.
diff --git a/src/tools-support/release-notes/api/archive/2023-04-07.md b/src/tools-support/release-notes/api/archive/2023-04-07.md
index bc43139b1a..e86e61f136 100644
--- a/src/tools-support/release-notes/api/archive/2023-04-07.md
+++ b/src/tools-support/release-notes/api/archive/2023-04-07.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, April 2023
 layout: reference
 ---
@@ -38,7 +38,7 @@ The decommission of Get Expense Entries List v1.1 API is planned for May 31st, 2
  
 ### Planned Change: Decommission of Get Location v1.1
 
-The decommission of Get Locations v1.1 API is planned for May 31st, 2023. If applicable, please work with your SAP Concur representative to move to [Get Locations v3](/api-reference/common/locations/v3.locations) as soon as possible.
+The decommission of Get Locations v1.1 API is planned for May 31st, 2023. If applicable, please work with your SAP Concur representative to move to [Get Locations v3](/api-reference/common/locations/v3.locations.html) as soon as possible.
 
 ### Planned Change: Get Cost Object for Approver V4 API
 
@@ -80,12 +80,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation of Request APIs (v1.0, v3.0 and v3.1)|Effective March 1st, 2020, the Request APIs (v1.0, v3.0 and v3.1) have been deprecated. They have been replaced by [Request v4](/api-reference/request/v4.get-started.html). Decommission will follow on May 31st, 2023.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation of Request APIs (v1.0, v3.0 and v3.1)|Effective March 1st, 2020, the Request APIs (v1.0, v3.0 and v3.1) have been deprecated. They have been replaced by [Request v4](/api-reference/request/v4.get-started.html). Decommission will follow on May 31st, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission will follow on November 10th, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -96,4 +96,4 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
diff --git a/src/tools-support/release-notes/api/archive/2023-05-04.md b/src/tools-support/release-notes/api/archive/2023-05-04.md
index 882b52f6ed..6f08f7e194 100644
--- a/src/tools-support/release-notes/api/archive/2023-05-04.md
+++ b/src/tools-support/release-notes/api/archive/2023-05-04.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, May 2023
 layout: reference
 ---
@@ -65,13 +65,13 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Decommission of Get Expense Entries List v1.1|The decommission of Get Expense Entries List v1.1 API is planned for May 31st, 2023. If applicable, please work with your SAP Concur representative to move to [Retrieve Expenses on a Specific Report ID](/api-reference/expense/expense-report/v4.expenses.html#retrieve-expenses-on-a-specific-report-id-) as soon as possible.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Decommission of Get Location v1.1|The decommission of Get Locations v1.1 API is planned for May 31st, 2023. If applicable, please work with your SAP Concur representative to move to [Get Locations v3](/api-reference/common/locations/v3.locations) as soon as possible.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Decommission of Get Expense Entries List v1.1|The decommission of Get Expense Entries List v1.1 API is planned for May 31st, 2023. If applicable, please work with your SAP Concur representative to move to [Retrieve Expenses on a Specific Report ID](/api-reference/expense/expense-report/v4.expenses.html#retrieve-expenses-on-a-specific-report-id-) as soon as possible.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Decommission of Get Location v1.1|The decommission of Get Locations v1.1 API is planned for May 31st, 2023. If applicable, please work with your SAP Concur representative to move to [Get Locations v3](/api-reference/common/locations/v3.locations.html) as soon as possible.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -82,6 +82,6 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
diff --git a/src/tools-support/release-notes/api/archive/2023-06-02.md b/src/tools-support/release-notes/api/archive/2023-06-02.md
index aafb03916e..be2716f459 100644
--- a/src/tools-support/release-notes/api/archive/2023-06-02.md
+++ b/src/tools-support/release-notes/api/archive/2023-06-02.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, June 2023
 layout: reference
 ---
@@ -22,7 +22,7 @@ We have modified the “statusChanged” events that are published for workflow
 
 ### Mexico CFDI Integration Guide Now Available
 
-We have added a guide to provide additional information for our [Mexico CFDI integration](/api-guides/expense/mexico-cfdi-integration).
+We have added a guide to provide additional information for our [Mexico CFDI integration](/api-guides/expense/mexico-cfdi-integration.html).
 
 ### Deprecation of Launch External URL Callout v1
 
@@ -34,7 +34,7 @@ The decommission of Get Expense Entries List v1.1 API occurred on May 31st, 2023
 
 ### Decommission of Get Location v1.1
 
-The decommission of Get Locations v1.1 API occurred on May 31st, 2023. This has been replaced by [Get Locations v3](/api-reference/common/locations/v3.locations).
+The decommission of Get Locations v1.1 API occurred on May 31st, 2023. This has been replaced by [Get Locations v3](/api-reference/common/locations/v3.locations.html).
 
 ### List Item Bulk V4 API Now Available
 
@@ -91,11 +91,11 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -106,8 +106,8 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|End of life Legacy Agency Proposal integrated with Concur Request (relying on trip v1.1 API)|After June 30th, 2023, the Legacy Agency Proposal feature relying on the Trip v1.1 API will no longer be available in Production.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|End of life Legacy Agency Proposal integrated with Concur Request (relying on trip v1.1 API)|After June 30th, 2023, the Legacy Agency Proposal feature relying on the Trip v1.1 API will no longer be available in Production.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
diff --git a/src/tools-support/release-notes/api/archive/2023-07-12.md b/src/tools-support/release-notes/api/archive/2023-07-12.md
index 231db2b818..81d247b4f1 100644
--- a/src/tools-support/release-notes/api/archive/2023-07-12.md
+++ b/src/tools-support/release-notes/api/archive/2023-07-12.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, July 2023
 layout: reference
 ---
@@ -90,12 +90,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -106,9 +106,9 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
diff --git a/src/tools-support/release-notes/api/archive/2023-08-10.md b/src/tools-support/release-notes/api/archive/2023-08-10.md
index 527c94e5fd..c01d3a568b 100644
--- a/src/tools-support/release-notes/api/archive/2023-08-10.md
+++ b/src/tools-support/release-notes/api/archive/2023-08-10.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, August 2023
 layout: reference
 ---
@@ -97,12 +97,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -113,9 +113,9 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
diff --git a/src/tools-support/release-notes/api/archive/2023-09-07.md b/src/tools-support/release-notes/api/archive/2023-09-07.md
index d6bed9e91c..838a80e6ea 100644
--- a/src/tools-support/release-notes/api/archive/2023-09-07.md
+++ b/src/tools-support/release-notes/api/archive/2023-09-07.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, September 2023
 layout: reference
 ---
@@ -140,12 +140,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -156,9 +156,9 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
diff --git a/src/tools-support/release-notes/api/archive/2023-10-12.md b/src/tools-support/release-notes/api/archive/2023-10-12.md
index 738d0944b5..ed888b241d 100644
--- a/src/tools-support/release-notes/api/archive/2023-10-12.md
+++ b/src/tools-support/release-notes/api/archive/2023-10-12.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, October 2023
 layout: reference
 ---
@@ -109,12 +109,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -125,11 +125,11 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
 
diff --git a/src/tools-support/release-notes/api/archive/2023-11-02.md b/src/tools-support/release-notes/api/archive/2023-11-02.md
index ee917b97be..6067ea68a6 100644
--- a/src/tools-support/release-notes/api/archive/2023-11-02.md
+++ b/src/tools-support/release-notes/api/archive/2023-11-02.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, November 2023
 layout: reference
 ---
@@ -76,12 +76,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -95,11 +95,11 @@ Date|API|Planned Change
 [10/2023](tools-support/release-notes/api/2023-10-12.html)|Expense Exceptions v4 API|In December, 2023, we will be releasing an API to manage exceptions on reports, entries, and allocations.  We will be releasing PUT, GET, and DELETE exceptions for reports, entries, and allocations.
 [10/2023](tools-support/release-notes/api/2023-10-12.html)|Ready for Integration Event|Authorized consumers of the Financial Integration Service v4 API can subscribe to a new event that will notify them when a financial posting document is ready and available for import.
  [10/2023](tools-support/release-notes/api/2023-10-12.html)|Workflow v4|An upcoming documentation update will add a Workflow v4 page under the existing Expense v4 category. This page will be populated with existing expense workflow APIs, such as the Approve or Send Back a Report API, which historically has been a section on the Reports v4 page.
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
 
diff --git a/src/tools-support/release-notes/api/archive/2023-12-14.md b/src/tools-support/release-notes/api/archive/2023-12-14.md
index 14952ac395..94237443f4 100644
--- a/src/tools-support/release-notes/api/archive/2023-12-14.md
+++ b/src/tools-support/release-notes/api/archive/2023-12-14.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, December 2023
 layout: reference
 ---
@@ -70,12 +70,12 @@ APIs are being deprecated in accordance with the [SAP Concur API Lifecycle & Dep
 
 Date|API|Details
 ---|---|---
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[12/2022](/tools-support/release-notes/api/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[11/2022](/tools-support/release-notes/api/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
-[10/2022](/tools-support/release-notes/api/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Deprecation and Decommission of Vendor v3|Vendor v3 is being deprecated and decommissioned, users will have until November 30, 2023 to migrate to the latest version of the API.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of Cash Advance v4|Effective October 1st, 2022, the Cash Advance v4 API is deprecated. This has been replaced by the release of [Cash Advance v4.1](/api-reference/cash-advance/v4-1.cash-advance.html). Decommission will follow on October 2, 2023.
+[10/2022](/tools-support/release-notes/api/archive/2022-10-14.html)|Deprecation of  Hotel Service v2|Effective October 14th, 2022, the Hotel Service v2 API is deprecated. This has been replaced by the release of [Hotel Service v4](/api-reference/direct-connects/hotel-service-4/v4.getting-started.html). Decommission will follow on October 16, 2023.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-deprecation)|List v3 API|Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the [List v4](/api-reference/common/lists/v4.list.html) API. List v3 is planned to be retired in a future release.
 [01/2021](/tools-support/release-notes/api/archive/2021-01-22.html#planned-list-item-deprecation)|List Item v3 API|Effective April 16, 2021, we have deprecated the List Item v3 API. This API is replaced by the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API. List Item v3 is planned to be retired in a future release. Please migrate to the [List Item v4](/api-reference/common/list-item/v4.list-item.html) API as soon as possible.
@@ -86,13 +86,13 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[11/2023](https://developer.concur.com/tools-support/release-notes/api/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
+[11/2023](https://developer.concur.com/tools-support/release-notes/api/archive/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
  [10/2023](tools-support/release-notes/api/2023-10-12.html)|Workflow v4|An upcoming documentation update will add a Workflow v4 page under the existing Expense v4 category. This page will be populated with existing expense workflow APIs, such as the Approve or Send Back a Report API, which historically has been a section on the Reports v4 page.
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
-[02/03/23](/tools-support/release-notes/api/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Managed List|We will be releasing additional functionality to our list services with Managed Lists. A Managed List is a list in which all modifications to the list are restricted to a single app ID.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[02/03/23](/tools-support/release-notes/api/archive/2023-02-03.html)|New Itinerary v4 API Endpoint for List of Trips with Travel Dates in a Specified Date Range|We will be introducing a new endpoint for the Itinerary v4 API to provide a list of company trips with travel dates in a specified date range. This additional functionality will provide customers and partners with a scalable, performant, and self-serve way to retrieve a list of trips with travel dates in a specified range as they onboard companies.
 
diff --git a/src/tools-support/release-notes/api/archive/2024-01-11.md b/src/tools-support/release-notes/api/archive/2024-01-11.md
index 470e797f9d..61580df9af 100644
--- a/src/tools-support/release-notes/api/archive/2024-01-11.md
+++ b/src/tools-support/release-notes/api/archive/2024-01-11.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, January 2024
 layout: reference
 ---
@@ -53,11 +53,11 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)|The decommission of the v1.0, v3.0, and v3.1 APIs is planned to conclude soon. Users that have not yet migrated to the Concur Request v4 APIs are strongly encouraged to make the required developments. 
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
@@ -73,10 +73,10 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[11/2023](https://developer.concur.com/tools-support/release-notes/api/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
+[11/2023](https://developer.concur.com/tools-support/release-notes/api/archive/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
  [10/2023](tools-support/release-notes/api/2023-10-12.html)|Workflow v4|An upcoming documentation update will add a Workflow v4 page under the existing Expense v4 category. This page will be populated with existing expense workflow APIs, such as the Approve or Send Back a Report API, which historically has been a section on the Reports v4 page.
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Payroll Integration Available Without Integration with Concur Solutions (ICS)|Payroll fields will be available through the Financial Integration Service (FIS) API. This allows users of the FIS API (partner apps or customers with custom integrations) to also use the API for payroll integration.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
diff --git a/src/tools-support/release-notes/api/archive/2024-02-08.md b/src/tools-support/release-notes/api/archive/2024-02-08.md
index 086456cd00..f9d8a8fdb2 100644
--- a/src/tools-support/release-notes/api/archive/2024-02-08.md
+++ b/src/tools-support/release-notes/api/archive/2024-02-08.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, February 2024
 layout: reference
 ---
@@ -36,11 +36,11 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)|The decommission of the v1.0, v3.0, and v3.1 APIs is planned to conclude soon. Users that have not yet migrated to the Concur Request v4 APIs are strongly encouraged to make the required developments. 
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
@@ -56,10 +56,10 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[01/2024](https://developer.concur.com/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
-[11/2023](/tools-support/release-notes/api/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
-[10/2023](/tools-support/release-notes/api/2023-10-12.html)|Workflow v4|An upcoming documentation update will add a Workflow v4 page under the existing Expense v4 category. This page will be populated with existing expense workflow APIs, such as the Approve or Send Back a Report API, which historically has been a section on the Reports v4 page.
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[01/2024](https://developer.concur.com/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[11/2023](/tools-support/release-notes/api/archive/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
+[10/2023](/tools-support/release-notes/api/archive/2023-10-12.html)|Workflow v4|An upcoming documentation update will add a Workflow v4 page under the existing Expense v4 category. This page will be populated with existing expense workflow APIs, such as the Approve or Send Back a Report API, which historically has been a section on the Reports v4 page.
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
diff --git a/src/tools-support/release-notes/api/archive/2024-03-14.md b/src/tools-support/release-notes/api/archive/2024-03-14.md
index d9d2e746f7..c961ee8aa5 100644
--- a/src/tools-support/release-notes/api/archive/2024-03-14.md
+++ b/src/tools-support/release-notes/api/archive/2024-03-14.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, March 2024
 layout: reference
 ---
@@ -30,11 +30,11 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)|The decommission of the v1.0, v3.0, and v3.1 APIs is planned to conclude soon. Users that have not yet migrated to the Concur Request v4 APIs are strongly encouraged to make the required developments. 
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
@@ -50,10 +50,10 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[01/2024](https://developer.concur.com/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
-[11/2023](/tools-support/release-notes/api/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
-[10/2023](/tools-support/release-notes/api/2023-10-12.html)|Workflow v4|An upcoming documentation update will add a Workflow v4 page under the existing Expense v4 category. This page will be populated with existing expense workflow APIs, such as the Approve or Send Back a Report API, which historically has been a section on the Reports v4 page.
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
+[01/2024](https://developer.concur.com/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[11/2023](/tools-support/release-notes/api/archive/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
+[10/2023](/tools-support/release-notes/api/archive/2023-10-12.html)|Workflow v4|An upcoming documentation update will add a Workflow v4 page under the existing Expense v4 category. This page will be populated with existing expense workflow APIs, such as the Approve or Send Back a Report API, which historically has been a section on the Reports v4 page.
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Approve Report, Send Back Report, and Recall Report v4 APIs|These APIs will replace the [expense report workflow action v1.1 API](/api-reference/expense/expense-report/post-report-workflow-action.html). These v4 expense report workflow APIs are functionally similar to their v1 Post an Expense Report Workflow Action counterparts but will be available as separate actions. 
diff --git a/src/tools-support/release-notes/api/archive/2024-04-04.md b/src/tools-support/release-notes/api/archive/2024-04-04.md
index 65a3ec16f8..31d3e3d57d 100644
--- a/src/tools-support/release-notes/api/archive/2024-04-04.md
+++ b/src/tools-support/release-notes/api/archive/2024-04-04.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, April 2024
 layout: reference
 ---
@@ -64,12 +64,12 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)|The decommission of the v1.0, v3.0, and v3.1 APIs is planned to conclude soon. Users that have not yet migrated to the Concur Request v4 APIs are strongly encouraged to make the required developments. 
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
@@ -85,8 +85,8 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[01/2024](https://developer.concur.com/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
-[11/2023](/tools-support/release-notes/api/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
\ No newline at end of file
+[01/2024](https://developer.concur.com/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[11/2023](/tools-support/release-notes/api/archive/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
\ No newline at end of file
diff --git a/src/tools-support/release-notes/api/archive/2024-05-09.md b/src/tools-support/release-notes/api/archive/2024-05-09.md
index f6cb189bdc..f67f3e1e0d 100644
--- a/src/tools-support/release-notes/api/archive/2024-05-09.md
+++ b/src/tools-support/release-notes/api/archive/2024-05-09.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, May 2024
 layout: reference
 ---
@@ -104,12 +104,12 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)|The decommission of the v1.0, v3.0, and v3.1 APIs is planned to conclude soon. Users that have not yet migrated to the Concur Request v4 APIs are strongly encouraged to make the required developments. 
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
@@ -125,8 +125,8 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[01/2024](https://developer.concur.com/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
-[11/2023](/tools-support/release-notes/api/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
-[04/2023](/tools-support/release-notes/api/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
\ No newline at end of file
+[01/2024](https://developer.concur.com/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[11/2023](/tools-support/release-notes/api/archive/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[04/2023](/tools-support/release-notes/api/archive/2023-04-07.html)|Get Cost Object for Approver v4 API|Externalizing this endpoint allows external callers to view a report's approver related cost objects within a cost object approval workflow.
\ No newline at end of file
diff --git a/src/tools-support/release-notes/api/archive/2024-06-06.md b/src/tools-support/release-notes/api/archive/2024-06-06.md
index fb47e24945..d3a04f8efd 100644
--- a/src/tools-support/release-notes/api/archive/2024-06-06.md
+++ b/src/tools-support/release-notes/api/archive/2024-06-06.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, June 2024
 layout: reference
 ---
@@ -122,12 +122,12 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)|The decommission of the v1.0, v3.0, and v3.1 APIs is planned to conclude soon. Users that have not yet migrated to the Concur Request v4 APIs are strongly encouraged to make the required developments. 
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
@@ -143,8 +143,8 @@ Date|API|Details
 
 Date|API|Planned Change
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
-[11/2023](/tools-support/release-notes/api/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
-[09/2023](/tools-support/release-notes/api/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
-[05/2023](/tools-support/release-notes/api/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[11/2023](/tools-support/release-notes/api/archive/2023-11-02.html)|Expense Report v1.1|We will be adding a new request query parameter `includeInactive={Y/N}` to return both active and inactive delegators for a particular delegate. If this parameter is not present the API will return only active delegators (no change from current behavior).
+[09/2023](/tools-support/release-notes/api/archive/2023-09-07.html)|Travel Profile API 2.0|All partners and customers currently using Travel Profile API 2.0 will need to prepare their systems to support two new Gender values: Unknown and Unspecified. The support for those new values is planned to be released in Q1 2024.
+[05/2023](/tools-support/release-notes/api/archive/2023-05-04.html)|Get Cost Objects Request v4 API|This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
diff --git a/src/tools-support/release-notes/api/archive/2024-07-10.md b/src/tools-support/release-notes/api/archive/2024-07-10.md
index 118e97f321..4d0e18e226 100644
--- a/src/tools-support/release-notes/api/archive/2024-07-10.md
+++ b/src/tools-support/release-notes/api/archive/2024-07-10.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, July 2024
 layout: reference
 ---
@@ -105,8 +105,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Planned Change
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -114,12 +114,12 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
-[07/2023](/tools-support/release-notes/api/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of Password Provisioning via File Import|The decommission of password provisioning via file import will occur on October 1st, 2023. 
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommissioning of Password Provisioning|Beginning August 2nd, 2023, password provisioning for user accounts will not be supported.
+[07/2023](/tools-support/release-notes/api/archive/2023-07-12.html)|Decommission of User v1 Password Endpoint|The decommission of the User v1 password endpoint will occur on July 28th, 2023.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [12/2022](/tools-support/release-notes/api/archive/2022-12-02.html)|Decommission of Existing Concur Request APIs (v1.0, v3.0, v3.1)|The decommission of the v1.0, v3.0, and v3.1 APIs is planned to conclude soon. Users that have not yet migrated to the Concur Request v4 APIs are strongly encouraged to make the required developments. 
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
diff --git a/src/tools-support/release-notes/api/archive/2024-08-08.md b/src/tools-support/release-notes/api/archive/2024-08-08.md
index f0f1041bc6..bc0aace4ce 100644
--- a/src/tools-support/release-notes/api/archive/2024-08-08.md
+++ b/src/tools-support/release-notes/api/archive/2024-08-08.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, August 2024
 layout: reference
 ---
@@ -103,8 +103,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Preview
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -112,9 +112,9 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
diff --git a/src/tools-support/release-notes/api/archive/2024-09-12.md b/src/tools-support/release-notes/api/archive/2024-09-12.md
index 824a3aea81..469dbbce76 100644
--- a/src/tools-support/release-notes/api/archive/2024-09-12.md
+++ b/src/tools-support/release-notes/api/archive/2024-09-12.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, September 2024
 layout: reference
 ---
@@ -67,8 +67,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Preview
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -76,9 +76,9 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
diff --git a/src/tools-support/release-notes/api/archive/2024-10-03.md b/src/tools-support/release-notes/api/archive/2024-10-03.md
index 8d52ab66e7..13415a0485 100644
--- a/src/tools-support/release-notes/api/archive/2024-10-03.md
+++ b/src/tools-support/release-notes/api/archive/2024-10-03.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, October 2024
 layout: reference
 ---
@@ -54,8 +54,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Preview
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -63,9 +63,9 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
diff --git a/src/tools-support/release-notes/api/archive/2024-11-07.md b/src/tools-support/release-notes/api/archive/2024-11-07.md
index 3ee3b7e452..27d39d04ab 100644
--- a/src/tools-support/release-notes/api/archive/2024-11-07.md
+++ b/src/tools-support/release-notes/api/archive/2024-11-07.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, November 2024
 layout: reference
 ---
@@ -43,8 +43,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Preview
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -52,9 +52,9 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.
diff --git a/src/tools-support/release-notes/api/archive/2024-12-05.md b/src/tools-support/release-notes/api/archive/2024-12-05.md
index c31a4e8f37..c451caf282 100644
--- a/src/tools-support/release-notes/api/archive/2024-12-05.md
+++ b/src/tools-support/release-notes/api/archive/2024-12-05.md
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, December 2024
 layout: reference
 ---
@@ -40,8 +40,8 @@ In general, this table lists items that will be shipping in the next 30-60 days.
 
 Date|API|Preview
 ---|---|---
-[05/2024](/tools-support/release-notes/api/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
-[01/2024](/tools-support/release-notes/api/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
+[05/2024](/tools-support/release-notes/api/archive/2024-05-09.html)|Retention Period for Credit Card Data Files|For compliance reasons, SAP Concur will be implementing a process wherein card data files received from external sources (Issuing banks, Card associations) will be deleted from systems after 90 days.
+[01/2024](/tools-support/release-notes/api/archive/2024-01-11.html)|Hotel Service v4|Updates to Hotel Service v4 that will remove existing elements from the <Profiles> section relating to gender and name prefixes.
 
 ## Deprecations and Decommissions
 
@@ -49,9 +49,9 @@ APIs are being deprecated or decommissioned in accordance with the [SAP Concur A
 
 Date|API|Details
 ---|---|---
-[03/2024](/tools/support/release-notes/api/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
-[06/2023](/tools-support/release-notes/api/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
-[01/2023](/tools-support/release-notes/api/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
+[03/2024](/tools-support/release-notes/api/archive/2024-03-14.html)|Deprecation of Spend User Retrieval 4.0.|The decommission of password provisioning via file import will occur in April 2025.
+[06/2023](/tools-support/release-notes/api/archive/2023-06-02.html)|Deprecation of Launch External URL Callout v1|The Launch External URL V1 API is deprecated as of June 16th, 2023. Decommission will follow.
+[01/2023](/tools-support/release-notes/api/archive/2023-01-05.html)|Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)|This callout was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the [Request events](https://developer.concur.com/api-reference/ess/v4.event-subscription.html).
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v1|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [11/2022](/tools-support/release-notes/api/archive/2022-11-10.html)|Deprecation of User v3|Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by [User Provisioning Service v4](/api-reference/user-provisioning/v4.user-provisioning.html). Decommission has been extended and will conclude on May 31st, 2024.
 [04/2021](/tools-support/release-notes/api/archive/2021-04-16.html#planned-deprecation-bulk-user)|Bulk User v3.1 API|We have deprecated the Bulk User v3.1 API for the US and EMEA data centers. This API is replaced by [Identity v4](/api-reference/profile/v4.identity.html). Decommission will follow. Bulk User v3.1 will remain available for China data centers.