API Release Notes, August 2022
New This Month
Migration of Test Entities & Production Sandbox Environment
Some SAP Concur users use Production Sandbox Environment (PSE) entities to set up, test, and train on new configurations prior to deploying them to their live production entity. SAP Concur plans to migrate PSEs as part of our move to Amazon Web Services (AWS). For more information, please see the Test Entities | Production Sandbox Environment release note in the August Shared Release Notes.
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).
Once the CHS provider has developed and certified their API implementation with SAP Concur, their content will be available to shop and book by opted-in Travel users.
SSL Certificates for us.api.concursolutions.com and emea.api.concursolutions.com Expiring (Aug 15 2022)
To ensure the ongoing security of our products and services, the current SSL certificates for us.api.concursolutions.com and emea.api.concursolutions.com are being renewed. The current certificates will expire on August 15, 2022.
Users who have not pinned the SSL certificates do not need to take any action as the certificates will be renewed automatically. Most users do not pin the certificates.
Users who have pinned the expiring certificates must renew the certificates before August 11, 2022 6 PM PST. If the pinned certificates are not updated before August 11, 2022 6PM PST, connections to SAP Concur products through SAP integration with Concur Services (SAP ICS) and Web Services might be disrupted. Please consult with your IT department to confirm whether this applies to you.
NOTE: Because SSL certificates are renewed on a regular basis to ensure the security of our products, pinning them is not recommended.
IP Address Range for Callouts
Beginning in August and continuing through the end of 2022, servers that support SAP Concur callouts in the US & EMEA datacenters will be upgraded. For more information on this release note, please see the August Shared Release Notes.
Planned Change: Spend Documents v4 API Available
The Spend Documents v4 API that will allow for the retrieval of compliance documents (GRDC and Fapiao) associated with expense transactions.
Ongoing
None
Deprecations
APIs are being deprecated in accordance with the SAP Concur API Lifecycle & Deprecation Policy.
| Date | API | Details |
|---|---|---|
| 09/2021 | 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 service. Both of these services enable callers to CRUD user’s core/identity profile information like UUID, name, address, email, etc. |
| 07/2021 | User v3 API | We will be deprecating the User v3 API in a future release due to less secure authentication methods. |
| 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. |
| 04/2020 | 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 | 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 |
|---|---|---|
| 05/2022 | 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 | 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 | 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 | 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 | 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 | 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. Date will be communicated in future communications. |
| 04/2021 | 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 | 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. |