API Release Notes, May 2023
New This Month
List Item Bulk V4 API Available
We have released the List Item Bulk V4 API. The List Item Bulk v4 API allows for creating and modifying multiple list items in a list. The currently published List Item v4 API provides functionality for creating, updating, and deleting a single list item.
New Field Added to Financial Integration Services (FIS) v4 API
A new field have been added to the Financial Integration Services (FIS) v4 API.
merchantTaxId provides additional tax information for expense reports.
The feature is automatically available; there are no additional configuration or activation steps.
Ongoing: 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. Decommission is now ongoing since June 1st, 2021 and the legacy Concur Request APIs (v1.0, v3.0, v3.1) will only be supported on a limited case-by-case basis. A new decommission date will be defined and the legacy Concur Request APIs (v1.0, v3.0, v3.1) will no longer be available into Production, in accordance with the SAP Concur API Lifecycle & Deprecation Policy.
API Timeline for v1.0, v3.0, v3.1:
- Deprecation – March 1, 2020 – May 31, 2021
- Decommission – Since June 01, 2021
The Concur Request APIs v1.0, v3.0 and v3.1 only support the previous authentication method, which is not best security practice and does not meet the OAuth2 standards. In addition, the previous versions of the Concur Request APIs provided limited possibilities for moving a Request through the approval workflow, as well as managing custom simple & connected list fields. These issues are resolved with the new Concur Request v4 APIs.
In addition, SAP has run a backward compatibility project between the current Concur Request APIs and the new Concur Request v4 APIs (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 APIs.
Please work with your Concur representative to move from your current legacy Concur Request APIs (v1.0, v3.0, v3.1) towards the Request v4 APIs.
Ongoing: Move from the Travel Request External Validation Callout v1 to the Event Subscription Service (ESS)
The Travel Request External Validation Callout v1 API was designed to work with the Concur Request v1 API that is in the process of being decommissioned. Users relying on the Travel Request External Validation Callout v1 are strongly recommended to move to the Event Subscription Services (ESS) in order to subscribe to the Request events.
Please work with your organization to move from Travel Request External Validation Callout v1 to Event Subscription Services (ESS).
For new users willing to take advantage of the Concur Request External Validation Workflow Feature, please work with your Concur representative to rely on the Concur Event Subscription Service and configure the Concur Request Workflow accordingly.
Planned Change: End of life Legacy Agency Proposal integrated with Concur Request (relying on trip v1.1 API)
During the last two years, SAP Concur has been working closely with travel agencies to migrate to the new agency proposal feature with Request v4 API. Existing users utilizing the agency proposal integration in Concur Request with their travel agencies have been migrated (or are currently being migrated) accordingly.
After June 30th, 2023, the Legacy Agency Proposal feature relying on the Trip v1.1 API will no longer be available in Production. Any travel agency willing to benefit from the agency proposal feature integrated with Concur Request will need to rely on the agency proposal feature within Request v4 API.
The Agency Proposals feature for Concur Request is a solution offered by SAP Concur to travel agencies in order to facilitate the interaction between travelers and their travel agents for offline bookings. However, the Agency Proposals feature requires developments on each travel agency’s side as well as a certification provided by SAP Concur. This solution cannot be offered to users before aligning with their travel agency to confirm the scope and countries managed on the travel agency’s side.
Travel agencies who are still relying on the Trip v1.1 API to interact with Concur Request for the agency proposal feature are already in the process of finalizing their migration. No additional action is expected from certified travel agencies and their clients after this migration.
For any questions regarding the travel agencies that are certified, please reach out to the SAP Concur Platform team.
Planned Change: Get Cost Objects Request v4 API
We will be releasing the Get Cost Objects for Request v4 API. This endpoint will allow external callers to view a Request’s approver related cost objects within a cost object approval workflow.
APIs are being deprecated in accordance with the SAP Concur API Lifecycle & Deprecation Policy.
|04/2023||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 as soon as possible.|
|04/2023||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 as soon as possible.|
|12/2022||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||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.|
|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.|
|02/03/23||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.|