Attendees v2

The attendees in the Concur company. This resource can be used to retrieve attendee information for any attendee in the Concur company, regardless of whether they are Private or Shared. In future releases, this resource will be enhanced to provide full attendee management functionality.

This API allows developers to manage attendees in Concur. The Attendee resource can be used to retrieve attendee information for private or shared attendees. In future releases, the Attendee resource will be updated with additional functionality for managing all attendees in Concur.

The Attendee resource manages attendees in batches, and can be used to add, update or inactivate attendees. This resource provides functionality similar to the Attendee List Import in Concur. Attendees added using this resource are added to the Shared Attendee List (owned by the system and available to all users).

Limitations

Access to this documentation does not provide access to the API. 

Product Restrictions

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.

See also

• Attendees v1
• Attendee Types v1

URI

https://www.concursolutions.com/api/expense/v2.0/attendees

Resources

• Attendees v2
• Attendees v1
• Attendee Types v1

Get attendees

Retrieves the attendees matching the specified search criteria. Developers can specify one or more External IDs or the Attendee ID to search the Expense database.

Request

Parameters

Examples:

https://www.concursolutions.com/api/expense/v2.0/attendees/{attendeeID}
https://www.concursolutions.com/apiexpense/v2.0/attendees?externalid={externalID}
https://www.concursolutions.com/apiexpense/v2.0/attendees?externalid={externalID1},{externalID2},{externalID3}

Headers

• RFC 7235 Authorization - Authorization header with OAuth 2.0 access token for a Concur user. Required. To manage data for an entire company, the Concur account associated with the access token must have one of these roles:
  • Web Services Administrator for Professional
  • Can Administer for Standard.
• RFC 7231 Content-Type: application/xml or application/json

Get Attendee Details Response

Content Types

• application/json
• application/xml

Content Body

This request will return an Attendees parent element containing an Attendee child element for each attendee.

Attendee elements

Custom elements

Examples

XML Example Request with Attendee ID

GET https://www.concursolutions.com/api/expense/v2.0/attendees/nFaAj0ncBsvkgnPMY5QWfBbbWyv$sQh2oW
Authorization: OAuth {token}

XML Example Request with External ID

GET https://www.concursolutions.com/api/expense/v2.0/attendees?externalid=234567
Authorization: OAuth {token}

XML Example of Successful Response

HTTP/1.1 200 OK
Content-Type: application/xml

<Attendees xmlns="http://www.concursolutions.com/api/expense/expensereport/2012/07" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
  <Attendee>
    <AttendeeType>BUSGUEST</AttendeeType>
    <FirstName>Chris</FirstName>
    <LastName>Miller</LastName>
    <Company />
    <Title />
    <ExternalID>234567</ExternalID>
    <Custom1 />
    <Custom2 />
    <Custom3 />
    <Custom4 />
    <Custom5 />
    <Custom6 />
    <Custom7 />
    <Custom8 />
    <Custom9 />
    <Custom10 />
    <Custom11 />
    <Custom12 />
    <Custom13 />
    <Custom14 />
    <Custom15 />
    <Custom16 />
    <Custom17 />
    <Custom18 />
    <Custom19 />
    <Custom20 />
    <HasExceptionsPrevYear>N</HasExceptionsPrevYear>
    <HasExceptionsYTD>N</HasExceptionsYTD>
    <IsDeleted>N</IsDeleted>
    <OwnerEmpName>Davis, Pat</OwnerEmpName>
    <TotalAmountPrevYear>0.00000000</TotalAmountPrevYear>
    <TotalAmountYTD>0.00000000</TotalAmountYTD>
    <VersionNumber>1</VersionNumber>
    <AttendeeID>nFaAj0ncBsvkgnPMY5QWfBbbWyv$sQh2oW</AttendeeID>
    <AttendeeTypeCode>BUSGUEST</AttendeeTypeCode>
    <AttendeeOwnerID>pd123456</AttendeeOwnerID>
    <CurrencyCode>USD</CurrencyCode>
  </Attendee>
</Attendees>

Responses and Errors

Refer to the HTTP Codes page for details of the common responses and errors.

Attendee List Errors

The web service will not return a 4xx HTTP response code for a batch operation even when every item in the batch failed to be created or updated. The client must inspect the response to look for warnings or errors with individual batch items.

When there are errors with batch items, the first ten errors are returned in the <errors> element in the request response, which includes their error code, the item that caused the error, and the error message. Any additional error messages are truncated. This prevents a large volume of error data in the event of a formatting mistake.

XML Response Error Codes