+
+
+
+ + + + + + + + + + +
+ + + +
+ + +

API Release Notes, July 2023

+ +

New This Month

+ +

Decommission of User v1 Password Endpoint

+ +

The decommission of the User v1 password endpoint will occur on July 28th, 2023. Clients that have not yet moved to the Concur Request v4 APIs will have until July 28th, 2023 to make the required changes. After the decommission date, the endpoint will no longer be available in Production, in accordance also with the SAP Concur API Lifecycle & Deprecation Policy.

+ +

Decommission of Default Password Generation of the Import Settings (Record Type 100)

+ +

The decommission of default password generation of the Import Settings (Record Type 100) will occur on July 28th, 2023. Users provisioning 305 and 350 import record types using password generation functionality will fail provisioning and not be loaded.

+ +

Please check your file provisioning to verify your default password generation setting or, work with your SAP Concur representative to verify the setting described in the Employee Import guide.

+ +

Preferred Name Available for Provisioning APIs (User Provisioning v4, Identity v4, & User v1)

+ +

We recognize that some employees may desire an alternative name by which they are addressed. This preferred name can be different from their legal name. We are updating our product to display preferred first name when provisioned (when allowed by country specific laws). Users may update their preferred name through the profile settings page.

+ +

Using the attribute displayName the name of the user, suitable for public display (givenName + familyName) when nickName is provisioned, nickName replaces givenName.

+ +

Reject Functionality Added to Expense v4

+ +

Expense v4 now provides the ability to reject a specific expense on a report. This will trigger the system to split the expense report into two separate reports – the existing report with the approved expenses, and a second report with the rejected expenses.

+ +

This functionality is provided by a new attribute isExpenseRejected, and can be set to true (to reject the expense), or false using the PATCH endpoint.

+ +

Additional Endpoint Added to Reports v4

+ +

A new endpoint has been added to the Reports v4 API. This enables an application built using SAP Concur APIs to POST a report.

+ +

Ongoing: Decommission of Password Provisioning via File Import

+ +

The decommission of password provisioning via file import will occur on October 1st, 2023. This will affect flat file imports, XLS imports, and the User v1 API. Please work with your SAP Concur representative if you have any questions.

+ +

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.

+ +

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.

+ +

Deprecations

+ +

APIs are being deprecated in accordance with the SAP Concur API Lifecycle & Deprecation Policy.

+ +