API Release Notes, March 2024
New This Month
Now Available: Post and Delete Expense Attendee Associations v4 API
We have released APIs to Post and Delete Expense Attendee Associations. These APIs will enable a partner application to add and remove attendees associated with an expense.
Now Available: Get Request Associations v4 API
We have released an API to Get the Request Associations on a Report. This APIs will enable a partner application to Get all the requests that are associated with a report.
Now Available: Spend User Retrieval v4.1
We have released a 4.1 version of Spend User Retrieval to retrieve spend profile data. This release is to meet standard software attribute naming protocols for orgUnitX attributes. There is no change in functionality of the spend user extension.
Deprecation of Spend User Retrieval 4.0
Effective March 14, 2024, the Spend User Extension 4.0 API has been deprecated. This has been replaced by Spend User Retrieval 4.1. Decommission will follow in April 2025.
Ongoing
Not applicable.
Deprecations and Decommissions
APIs are being deprecated or decommissioned in accordance with the SAP Concur API Lifecycle & Deprecation Policy.
| Date | API | Details |
|---|---|---|
| 07/2023 | Decommission of Password Provisioning via File Import | The decommission of password provisioning via file import will occur on October 1st, 2023. |
| 07/2023 | Decommissioning of Password Provisioning | Beginning August 2nd, 2023, password provisioning for user accounts will not be supported. |
| 07/2023 | Decommission of User v1 Password Endpoint | The decommission of the User v1 password endpoint will occur on July 28th, 2023. |
| 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. |
| 12/2022 | 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 | Deprecation of User v1 | Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by User Provisioning Service v4. Decommission has been extended and will conclude on May 31st, 2024. |
| 11/2022 | Deprecation of User v3 | Effective November 10th, 2022, the User v1 API has been deprecated. This has been replaced by User Provisioning Service v4. Decommission has been extended and will conclude on May 31st, 2024. |
| 10/2022 | 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. Decommission will follow on October 2, 2023. |
| 10/2022 | 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. Decommission will follow on October 16, 2023. |
| 04/2021 | 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. Decommission will follow. Bulk User v3.1 will remain available for China data centers. |
| 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. |
| 06/2020 | Travel Profile Notification v1 API | We are deprecating the Travel Profile Notification v1 APIs due to low usage. |
| 01/2020 | List v1 API | We will be retiring the List v1 API in a future release. This API is replaced by the List v4 API. |
Planned Changes
| Date | API | Planned Change |
|---|---|---|
| 01/2024 | Hotel Service v4 | Updates to Hotel Service v4 that will remove existing elements from the |
| 11/2023 | 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 | 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 | 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 | 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 | 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 | Approve Report, Send Back Report, and Recall Report v4 APIs | These APIs will replace the expense report workflow action v1.1 API. 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. |