The Concur Fetch Attendee version 2.0 callout allows clients to import attendee information from their internal system to Concur when a user is adding attendees to an entry. The Concur service sends the attendee search fields to an application connector, created by the client, a third-party developer, or 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 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 Concur. The user sees the list of matches and can select the appropriate attendee for the entry.
This callout differs from the standard Concur web services in the following ways:
- It uses an outbound message where Concur calls a public facing API endpoint provided by the application connector. Refer to Callouts > Core Concepts for more information.
- The client or third-party developers can configure and maintain the public web service interface (the application connector), or the connector can be maintained by Concur. This documentation specifies the request and response format required by Concur.
- Clients can either choose to create their own application connector using PHP, Java, .NET etc or can use one of Concur Partner’s Attendee Fetch applications.
- The client Concur Administrator must select the attendee types that will use this functionality during application connector registration. Once the attendee types are selected, they will be automatically configured to not allow users to create new attendees manually.
Works With These Concur Products
- Expense for Concur Professional/Premium
- Expense for Concur Standard
- Expense for Mobile
- Request for Concur Professional/Premium
- Concur products are highly configurable, and not all clients will have access to all features.
- Partner developers must determine which configurations are required for their solution prior to the review process.
- Existing clients can work with Concur Advantage Technical Services to create custom applications that work with their configuration.
Concur Connect Callout Details
Information on how to download, install, and configure the application connector is included in Callouts > Core Concepts.
Fetch Attendee Process Overview
The configuration process has the following steps:
- Client, third party developer, or Concur downloads, installs, configures, and customizes the application connector.
- Optional for Professional / Premium Only: Client Concur admin creates a new attendee type to use with the connector.
- Client registers the application connector, selecting the attendee types that will use the connector.
Once the configuration is complete, the callout uses the following process:
- The user selects the appropriate attendee type in the Search Attendees window.
- The user enters information into an attendee field and clicks Search.
- Concur sends the attendee search field information to the application connector. This request includes all attendee fields, with any blank values formatted as an empty string.
- The application connector queries the attendee system of record and returns a list of results to Concur.
NOTE: The results list is limited to 100 records.
- Concur displays the results in the Search Results section of the Search Attendees window.
NOTE: If the application connector does not respond or returns an error, the user is notified in a popup window within Concur.
Concur will not resend the request unless the user manually initiates the search again.
- If the user adds the attendees to the entry, the attendee information is saved in Concur.
Concur will make calls to the application connector’s endpoint using SSL. During configuration, Concur will connect to the application connector to validate that its hostname and access credentials are valid.
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 Concur can access the connector.
Authentication between 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 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 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 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 Concur to send the attendee search request to.
The client then registers the application connector with Concur:
- Log in to Concur as an administrative user.
- Select Administration > Web Services.
- Click Manage Application Connectors.
- Click New.
- Fill out the fields according to the Application Connector Fields table shown below.
- In the Services section, select Fetch Attendee.
- Click Configure. The Configure Service window appears.
- Enter the endpoint that the Concur will connect to on your server. Example:
- Select the Active check box if the endpoint is ready for use. Usually you will do this after you have implemented and tested the endpoint in your application connector.
- Select the attendee types that will use the application connector. These attendee types will be automatically configured to not allow users to create new attendees manually.
- Click OK.
- Click Test Connection. Concur will attempt to access the configured endpoint with the provided user credentials.
- Click Save. The application connector is now registered with Concur and enabled.
Application Connector Fields
||Enter the name that should appear in the list of connectors.
||Enter the description of the function of the connector, such as what back-end system it might connect to.
||Enter the hostname for the connector. Example:
||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.
||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 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.
Responses and Errors
Refer to the HTTP Codes page for details of the common responses and errors.