Effective December 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 APIs.
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 Concur 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.
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 will be deprecated automatically in a future release, in accordance with the SAP Concur API Lifecycle & Deprecation Policy.
To ensure the ongoing security of our products and services, beginning on June 22, 2020, SAP Concur solutions will no longer support connections to * .concursolutions.com and * api.concursolutions.com that use the following TLSv1.2 ciphers:
This update provides ongoing security for our products and services.
In order to ensure that connections to * .concursolutions.com and * api.concursolutions.com are not disrupted, clients and partners who currently connect to * .concursolutions.com or * api.concursolutions.com through an application that uses an unsupported cipher must upgrade the application to a supported cipher before June 22, 2020.
The following ciphers are supported: