Migrate from deprecated SAP Concur Invoice vendor API endpoints

Naga Sri Hari Gonaboyina

Updated September 26, 2024 14:53

SAP Concur Invoice deprecated the Vendor v3.0 API on January 13, 2023, which has been replaced with Vendor v3.1 API. You can use the existing API until it is decommissioned, which is planned on November 30, 2023. Hence, it is recommended that all the SAP Concur Invoice administrators should migrate the existing API with the new API at the earliest opportunity.

This article explains how to find the existing deprecated API in the existing flows and replace it with the new version API.

Additional references:

SAP Concur Invoice replacement endpoints

The following table lists the endpoints scheduled for retirement in the near future:

Deprecated endpoints v3.0	Replacement endpoints v3.1
Retrieve an Existing Vendor	Retrieve an Existing Vendor
Create Vendors	Create Vendors
Create or Update Vendor	Create or Update Vendor
Update Existing Vendors	Update Existing Vendors
Delete Vendor	Delete Vendor

Changes to make in integrator.io

When you encounter a deprecated endpoint, first copy the path parameter to a reference document as a backup when replacing the endpoint, following the instructions in the next sections.

A. New field mappings

According to the SAP Concur Invoice changes, Celigo has updated the relative URL of the Vendor API and made CountryCode and CurrencyCode fields mandatory to the POST operations. Hence, verify all the POST mappings in your existing flows and update these fields respectively.

New field mappings

B. Find the endpoint in the existing flows

To find an export that uses an SAP Concur Invoice connection:

Sign in to your integrator.io account.
Navigate to Resources > Connections.
Search for an existing Concur Invoice connection. From the Actions overflow ... menu, select Used by. A list of all items that use this connection appears.
Right-click the first flow step in the list and select your browser’s option to open it in a new tab.
Replace the configuration for the deprecated endpoints with the endpoints provided in the table above.

Example of each type of parameter replacement

Search parameters used in deprecated operations

Path parameters used in deprecated operations

Search parameters updated in replacement operations

Path parameters used in replacement operations

C. Update flows to use replacement endpoint

For each export and import that is using a deprecated API name and operation, find its corresponding replacement API name and operation in the chart below, and select the new API name and operation.

Deprecated		Replacement
API name	Operation	API name	Operation
Invoice: Vendor (Export)	Retrieve an existing vendor	Invoice: Vendor (Export)	Retrieve an existing vendor
Invoice: Vendor (Import)	Create Vendors	Invoice: Vendor (Import)	Create Vendors
Invoice: Vendor (Import)	Create or Update Vendor	Invoice: Vendor (Import)	Create or Update Vendor
Invoice: Vendor (Import)	Update Existing Vendors	Invoice: Vendor (Import)	Update Existing Vendors
Invoice: Vendor (Import)	Delete Vendor	Invoice: Vendor (Import)	Delete Vendor