SAP-docs · CelesteCasali · Apr 20, 2026
diff --git 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
@@ -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/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/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/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,16 +184,16 @@ 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
 
 APIs are being deprecated or decommissioned in accordance with the [SAP Concur API Lifecycle & Deprecation Policy](/tools-support/deprecation-policy.html).
 
 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
@@ -1,4 +1,4 @@
----
+---
 title: SAP Concur Developer Center - API Release Notes, February 2025
 layout: reference
 ---
@@ -123,16 +123,16 @@ 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
 
 APIs are being deprecated or decommissioned in accordance with the [SAP Concur API Lifecycle & Deprecation Policy](/tools-support/deprecation-policy.html).
 
 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.