The Concur Fetch Attendee version 2.0 callout allows clients to import attendee information from their internal system to SAP Concur when a user is adding attendees to an entry. The SAP Concur service sends the attendee search fields to an application connector, created by the client, a third-party developer, or SAP Concur. The connector is hosted by the client or third-party developer, and has access to the attendee system of record. The connector uses the attendee information sent from SAP Concur to search for all matching attendee records in the client’s system. Once the connector has the list of possible matches, it sends the attendee data to SAP Concur. The user sees the list of matches and can select the appropriate attendee for the entry.
This callout differs from the standard SAP Concur web services in the following ways:
Information on how to download, install, and configure the application connector is included in Callouts > Core Concepts.
The configuration process has the following steps:
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. You will need to install the signed certificate before SAP Concur can access the connector.
Authentication between SAP Concur and the application connector is performed using HTTP Basic Auth. By default, these credentials are stored in the appropriate web configuration file for your platform, such as web.xml or web.config. These credentials are entered in SAP Concur on the Register Application Connector page in Web Services under Administration.
Refer to the Installation Process for more information.
Version 3.0: Post Attendee Search Request
The installation process includes installing the application connector, and registering it with SAP Concur.
First, the client or third-party developer will create and install the application connector on their web site or a third party hosting site. The connector should be programmed to accept the requests from SAP Concur and provide the documented responses.
During installation, the client or developer will select and configure an externally available endpoint on the host server for SAP Concur to send the attendee search request to.
The client then registers the application connector with SAP Concur:
/attendee/v2.0/fetch
. Note: The endpoint name should contain ‘v2.0’, otherwise the API defaults to v1.0 and returns a different set of fields.Application Connector Fields
Field | Description |
---|---|
Name | Enter the name that should appear in the list of connectors. |
Description | Enter the description of the function of the connector, such as what back-end system it might connect to. |
Host Name | Enter the hostname for the connector. Example: https://{servername} |
User Name | Enter the user name required to authenticate with the host. This must be the same as the user name specified in the configuration file for the application connector, using HTTP Basic Auth. |
Password | Enter the password required to authenticate with the host. This must be the same as the password specified in the configuration file for the application connector, using HTTP Basic Auth.1.0 |
The SAP Concur administrator can select which attendee types use the connector when registering the application connector. These attendee types will be automatically configured to not allow users to create new attendees manually.
Professional/Premium Only: If desired, the administrator can create a new attendee type specifically for use with the connector.
Refer to the HTTP Status Codes for details of the common responses and errors.