API Release Notes, February 2026
New This Month
Preview: API Deprecation Headers
For APIs in deprecation, responses may include an x-api-warn header that identifies the deprecated endpoint and its recommended replacement. A sunset header will specify the planned decommission date and include a link to additional deprecation details, in compliance with SAP API policies. This will be applied to both API and UI gateways. For example:
-
x-api-warn: ‘/api/v3.1/travelrequest/’ is deprecated; use ‘/travelrequest/v4/’. See ‘https://developer.concur.com/tools-support/release-notes/api/archive/2023-01-05.html’ for details.
-
sunset: Sun, 01 Mar 2020 00:00:00 GMT
Preview: Groundspan Trip Extras v4
The Trip Extras v4 API will offer travelers ground transportation booking options through a redirect to Groundspan.This feature will replace the legacy Groundspan Direct Connect. This redirect will require the consumption of the following APIs: Event Subscription Service v4, Concur Travel Booking Events, Identity Change Event,Identity v4, Travel Extension v4, Travel Profile v2, Receipts v4, Maestro v4, Trip Extras v4.
Ongoing
Preview: Removal of concur.profile and concur.app Fields from Access Tokens(JWTs)
Two fields will be removed from Access Tokens (JWTs) and ID Tokens: concur.profile and concur.app. These fields currently contain fully formed URLs pointing to Profile v1 resources, for example:
- https://integration.api.concursolutions.com/profile/v1/principals/
- https://integration.api.concursolutions.com/profile/v1/apps/
These fields are being removed because the referenced URLs are no longer valid following the transition from Profile V1 to Profile v4. Also, these URLs were provided for convenience only and can be constructed using other information available in the JWT.
Target Dates
- Removal from Integration environments — week of March 23
- Removal from Production environments — week of April 6
Required Action
If your integration consumes either the concur.profile or concur.app fields from a JWT, update your implementation to remove this dependency by forming the necessary URL directly in your code.
Previews
In general, this table lists items that will be shipping in the next 30-60 days. For a broader view of features that are coming, please see our Road Map Explorer.
| Date | API | Preview |
|---|---|---|
| 01/2026 | Additions to Reservation and Search Requests in Hotel Service v4 | This API will add travel arranger details to a reservation request. It will also add the GIATA ID to a hotel search request. |
| 07/2025 | 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 | 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 | 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 | 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 | Hotel Service v4 | Updates to Hotel Service v4 that will remove existing elements from the |
Deprecations and Decommissions
APIs are being deprecated or decommissioned in accordance with the SAP Concur API Lifecycle & Deprecation Policy.
| Date | API | Details |
|---|---|---|
| 10/2025 | Deprecation of Locations v3 | Effective October 10, 2025, the Locations v3 API will be deprecated. This has been replaced by Localities v5. Decommission will follow. |
| 07/2025 | Deprecation of Expense Group Configurations v3 | Effective June 26, 2025, the Expense Group Configurations v3 API was deprecated. This has been replaced by the Expense Configuration v4 API. Decommission will follow. |
| 07/2025 | Deprecation of Expense v3 DELETE | Effective June 26, 2025, Expense v3 DELETE was deprecated. This has been replaced by Expense v4 Delete. Decommission will follow. |
| 07/2025 | 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 | 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 | 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 | Deprecation of Spend User Retrieval 4.0. | The decommission of password provisioning via file import will occur in April 2025. |
| 06/2023 | 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 | 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. |
| 01/2021 | List v3 API | Effective April 16, 2021, we have deprecated the List v3 API. This API is replaced by the List v4 API. List v3 is planned to be retired in a future release. |
| 01/2021 | 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. List Item v3 is planned to be retired in a future release. Please migrate to the List Item v4 API as soon as possible. |