Effective July 1, 2020, SAP Concur will be retiring the existing Concur Request APIs (v1.0, v3.0, and v3.1). These APIs are replaced by the Concur Request v4 API.
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 API.
In addition, SAP Concur has 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.
SAP Concur is deprecating the Travel Profile Notification v1 APIs due to low usage.
The Travel Profile Notification v1 APIs support older, less secure authentication methods.
The Travel Profile v1 APIs is being deprecated in accordance with the SAP Concur API Lifecycle & Deprecation Policy.
On November 12 (US) and November 13 (France), the F5 internal and external client SSL profiles for VIPs will be updated to remove support for the following protocols and ciphers:
Clients, TMCs, and internal SAP Concur employees who use or develop applications that rely on an F5 SSL client profile must test the ability of their applications to connect to SAP Concur entities using the new, more secure profile.
This update provides ongoing security for our products and services.
When this change is initially implemented, SAP Concur will make the following profiles available:
Clients, TMCs, and internal SAP Concur employees will be able to temporarily revert to the less secure profile to address any issues they encounter with the more secure profile before the less secure profile is permanently removed.
Previously, when the Travel Profile API was used to update cell phone numbers, parenthesis () and alphanumeric characters were allowed, including dashes and spaces. However, this sometimes resulted in duplicate phone number entries. With this change, SAP Concur solutions has reduced the allowed characters to dashes (-), spaces, and digits. This change reduces the likelihood of duplicate entries and makes the API behavior consistent with the User Profile Page behavior in the user interface.
This change provides a more consistent user experience and results in fewer bugs within the cell phone number entries process.
With this update, we have released API documentation for Rate Details for content providers to reference during development.
Content providers now have access to the documentation regarding details on how to retrieve rate data available through the Hotel Service API when serving content to customers on the SAP Concur Travel.