Concur Connection Requests API v3.1 Service Connector

Concur Connection Requests API v3.1 Service Connector

Posted by: Informatica Cloud Application Integration Team

TripLink allows travel suppliers to send itinerary data for connected users directly to Concur. This API allows TripLink suppliers to view, create, and update connection requests from Concur users.

Overview

Connection Requests Calls:

Endpoint 1: /common/connectionrequests

  • Gets all connection requests that match the TripLink supplier ID.
  • Method Path: /common/connectionrequests
  • HTTP Method: GET
  • Accepted content type(s): application/json

Endpoint 2: /common/connectionrequests

  • Creates a connection request on behalf of the specified user.
  • Method Path: /common/connectionrequests
  • HTTP Method: POST
  • Accepted content type(s): application/json

Endpoint 3: /common/connectionrequests/{id}

  • Gets a connection request by ID.
  • Method Path: /common/connectionrequests/{id}
  • HTTP Method: GET
  • Accepted content type(s): application/json

Endpoint 4: /common/connectionrequests/{id}

  • Updates the specified connection request. Only the fields provided in the supplied object are updated. Missing fields will not be altered.
  • Method Path: /common/connectionrequests/{id}
  • HTTP Method: PUT
  • Accepted content type(s): application/json

Features

Specifications

Security

SAP Concur will make calls to the application connector’s endpoint using SSL. During configuration, SAP Concur will connect to the application connector to validate that its hostname and access credentials are valid.

SAP Concur will not be able to connect to the application connector until a certificate signed by a Certificate Authority (CA) is installed in the application connector. If you are hosting the application connector, you will need to install the signed certificate before SAP Concur can access the connector.

Authentication

Authenticating to the application connector

Expense passes credentials using HTTP Basic Auth to authenticate with the application connector. By default, these credentials are stored in the appropriate web configuration file for your platform, such as web.xml or web.config. The steps to configure Expense with the credentials are detailed below.

Resources

Documentation

Support

Sorabh Agarwal

sagarwal@informatica.com