Concur Entry Attendee Associations API v3 Service Connector 

Concur Entry Attendee Associations API v3 Service Connector 

Posted by: Informatica Cloud Application Integration Team

Manage the relationship between the attendees and the expense report and entry, for the specified expense entry. This resource does not include the full attendee information, which can be accessed using the Attendees resource. This API provides methods to view, create, update, and delete entry attendee associations.

Overview

Entry Attendee Associations Calls:

Endpoint 1:/expense/entryattendeeassociations

  • Gets all entry-attendee associations owned by the user. These are the associations between an expense entry and an attendee.
  • Method Path: /expense/entryattendeeassociations
  • HTTP Method: GET
  • Accepted content type(s): application/json

Endpoint 2:  expense/entryattendeeassociations

  • Creates a new expense entry for the specified user.
  • Method Path : /expense/entryattendeeassociations
  • HTTP Method: POST
  • Accepted content type(s): application/json

Endpoint 3:  /expense/entryattendeeassociations/{id}

  • Deletes the specified entry-attendee association
  • Method Path: /expense/entryattendeeassociations/{id}
  • HTTP Method: DELETE
  • Accepted content type(s): application/json

Endpoint 4:/expense/entryattendeeassociations/{id}

  • Gets the specified expense entry-attendee association.
  • Method Path:  /expense/entries/{id}
  • HTTP Method: GET
  • Accepted content type(s): application/json

Endpoint 5:  /expense/entryattendeeassociations/{id}

  • Updates the specified entry-attendee association. Only the fields provided in the supplied object will be updated. Missing fields will not be altered.
  • Method Path:  /expense/entries/{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