Expense Entry Attendee v2

This API has been deprecated.

Partners and customers using a deprecated API should contact SAP Concur and discuss moving to the latest versions.

Learn more in the API Lifecycle & Deprecation Policy.

NOTE: Find the newer version 3.0 here.

The Expense Entry Attendees manages 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 Get Attendees function.

Limitations

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

URI

https://www.concursolutions.com/api/expense/expensereport/v2.0/report/{reportID}/entry/{entryID}/attendees

PUT Expense Entry Attendees

This allows the developer to specify which existing attendees are associated to the specified entry. It also gives the developer the option to provide the values for the Entry-Attendee association. The list of attendees in the request will replace any existing associated attendees, so the developer must include all attendees in the request. This function cannot be used to create new attendees.

Request

Parameters

Parameter Required/Optional Description
{_reportId_} Required The unique identifier for the expense report. This value is returned in the ReportID element by the Get Report Details function.
{_entryId_}/attendees Required The unique identifier for the expense entry and the Attendees keyword. This value is returned in the ReportEntryID element by the Get Report Details function.

Headers

  • Authorization - Authorization header with OAuth token for valid Concur user. The OAuth user must have one of the following roles in Expense:
    • Expense User: This role allows the user to modify their own reports.
    • Web Services Administrator (Professional/Premium): This role allows the user to modify reports for all users.
    • Can Administer (Standard/Sandbox): This role allows the user to modify reports for all users.
  • Content-Type
    • application/xml
    • application/json

Payload

XML: The request will contain an EntryAttendees parent element with an Attendee child element for each attendee associated to the entry.

JSON: The request string will contain an object for each attendee associated to the entry.

The request must include all attendees associated to the entry. To detach a previously attached attendee, use a Put request excluding the attendee. The function always associates only the attendees specified in the Put. To not modify the element or name/value pair value, provide a nill (XML) or null (JSON) value, or use the same value as you received in the Get Expense Entry Attendees response.

Attendee elements

The Attendee element (XML) or attendee object (JSON) must contain all of the following elements(XML) or name/value pairs(JSON):

Element Name Data Type Description
Amount decimal The portion of the Entry Transaction Amount assigned to this attendee.
AssociatedAttendeeCount int The count of attendees associated to this attendee. A count greater than 1 means there are unnamed attendees associated with this attendee.
AttendeeID string The unique identifier for the attendee.
EntryAttendeeCustom1 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.
EntryAttendeeCustom2 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.
EntryAttendeeCustom3 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.
EntryAttendeeCustom4 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.
EntryAttendeeCustom5 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.

Response

Headers

  • Content-Type
    • application/xml
    • application/json

Examples

XML example request

PUT https://www.concursolutions.com/api/expense/expensereport/v2.0/report/9d8ea1kole$sis293mn38dh/entry/8sle90wikl3h$halwnk$lakdjw83/attendees HTTP/1.1
Authorization: OAuth {access token}
Content-Type: application/xml
<EntryAttendees xmlns="http://www.concursolutions.com/api/expense/expensereport/2012/07" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
  <Attendee>
    <Amount>2422.00000000</Amount>
    <AssociatedAttendeeCount>1</AssociatedAttendeeCount>
    <AttendeeID>nFaAj0ncBso0sBd8ejqrxLHz1FfmhJ69b</AttendeeID>
    <EntryAttendeeCustom1>fg6rt</EntryAttendeeCustom1>
    <EntryAttendeeCustom2>9808</EntryAttendeeCustom2>
    <EntryAttendeeCustom3>64564drd</EntryAttendeeCustom3>
    <EntryAttendeeCustom4>352dsxcvs</EntryAttendeeCustom4>
    <EntryAttendeeCustom5 i:nil="true"/>
  </Attendee>
</EntryAttendees>

JSON example request

PUT https://www.concursolutions.com/api/expense/expensereport/v2.0/report/9d8ea1kole$sis293mn38dh/entry/8sle90wikl3h$halwnk$lakdjw83/attendees HTTP/1.1
Authorization: OAuth {access token}
Content-Type: application/json
[
  {
    "AttendeeID": "nFaAj0ncBs$puDs5XxZfOc6L5go8EJIueY",
    "Amount": "807.33000000",
    "AttendeeCount" :"0",
    "Custom1": "dfg",
    "Custom2": "7686",
    "Custom3": "89080990-90-5464",
    "Custom4": "56sdsd sf",
    "Custom5": null
  },
  {
    "AttendeeID": "nFaAj0ncBso0sBd8ejqrxLHz1FfmhJ69b",
    "Amount": "707.33000000",
    "AttendeeCount" :"0",
    "Custom1": "fg6rt",
    "Custom2": "9808",
    "Custom3": "64564drd",
    "Custom4": "352dsxcvs",
    "Custom5": null
  }
]

Example response

200 OK

GET Expense Entry Attendees

Retrieves the expense entry attendees for the specified expense entry. This function requires the v2.0 expense entry attendee resource.

Request

Parameters

Parameter Required/Optional Description
{_reportId_} Required The unique identifier for the expense report. This value is returned in the ReportID element by the Get Report Details function.
{_entryId_}/attendees Required The unique identifier for the expense entry and the Attendees keyword. This value is returned in the ReportEntryID element by the Get Report Details function.

Headers

  • Authorization header - Authorization header with OAuth token for valid Concur user. Required.
  • Content-Type
    • application/xml
    • application/json

Response

Headers

  • Content-Type
    • application/xml
    • application/json

Payload

This request will return an Attendees parent element with an Attendee child element for each attendee. The Attendee element will have the following child elements.

Element Name Data Type Description
Amount decimal The portion of the Entry Transaction Amount assigned to this attendee.
AssociatedAttendeeCount int The count of attendees associated to this attendee. A count greater than 1 means there are unnamed attendees associated with this attendee.
AttendeeID string The unique identifier for the attendee.
EntryAttendeeCustom1 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.
EntryAttendeeCustom2 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.
EntryAttendeeCustom3 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.
EntryAttendeeCustom4 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.
EntryAttendeeCustom5 string The value for Entry-Attendee custom fields 1-5. Varies based on configuration.

Examples

XML example request

GET https://www.concursolutions.com/api/expense/expensereport/v2.0/report/nxxKgLlnROz3zHJBCRksaas23dsfs/entry/n7We3qWw99u1KoWTMaLhSC$pXBYzQ1UDhn/attendees HTTP/1.1
Authorization: OAuth {access token}

JSON example request

GET https://www.concursolutions.com/api/expense/expensereport/v2.0/report/nxxKgLlnROz3zHJBCRksaas23dsfs/entry/n7We3qWw99u1KoWTMaLhSC$pXBYzQ1UDhn/Attendees HTTP/1.1
Authorization: OAuth {access token}

XML example response

HTTP/1.1 200 OK
Content-Type: application/xml
<EntryAttendees xmlns="http://www.concursolutions.com/api/expense/expensereport/2012/07" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
  <Attendee>
    <Amount>2422.00000000</Amount>
    <AssociatedAttendeeCount>1</AssociatedAttendeeCount>
    <AttendeeID>nFaAj0ncBso0sBd8ejqrxLHz1FfmhJ69b</AttendeeID>
    <EntryAttendeeCustom1>Medical</EntryAttendeeCustom1>
    <EntryAttendeeCustom2>North America</EntryAttendeeCustom2>
    <EntryAttendeeCustom3>Canada</EntryAttendeeCustom3>
    <EntryAttendeeCustom4>Vancouver</EntryAttendeeCustom4>
    <EntryAttendeeCustom5 i:nil="true"/>
  </Attendee>
</EntryAttendees>

JSON example response

HTTP/1.1 200 OK
Content-Type: application/json
[
  {
    "AttendeeID": "nFaAj0ncBs$puDs5XxZfOc6L5go8EJIueY",
    "Amount": "807.33000000",
    "AttendeeCount": "0",
    "Custom1": "Medical",
    "Custom2": "North America",
    "Custom3": "Canada",
    "Custom4": "Vancouver",
    "Custom5": null
  },
  {
    "AttendeeID": "nFaAj0ncBso0sBd8ejqrxLHz1FfmhJ69b",
    "Amount": "707.33000000",
    "AttendeeCount": "0",
    "Custom1": "Medical",
    "Custom2": "North America",
    "Custom3": "Canada",
    "Custom4": "Vancouver",
    "Custom5": null
  }
]

On this page