Skip to content
English
  • There are no suggestions because the search field is empty.

Attendee - Concur Data Target Requirement

Attendee - Concur Data Target Requirement

DataBlend supports the standard API calls to create an Attendee within Concur leveraging the Concur SDK. In addition, custom fields can be added for data that is unique to your business practices.

DataBlend Query Field Example Concur Object (API) Required Notes
Jane firstname Yes Max 50 characters.
Doe lastname Yes Max 132 characters.
fed46bff-8131-4d8b-977a-e81bc14268a4 id Yes, for Update The Concur attendee ID. Leave unmapped for Add operations.
kjdsahgkjsahgkjdsahg attendeetypeid Yes From GET /expense/attendeetypes. An attendee type cannot be changed on update.
BUSGUEST attendeetypecode No Code for the attendee type, e.g. EMPLOYEE, SPOUSE, BUSGUEST. Max 40 characters.
DataBlend company No Max 150 characters.
USD currencycode No 3-letter ISO 4217 currency code.
EXT-001 externalid No Unique identifier assigned outside Concur. Max 48 characters.
J middleinitial No Max 1 character.
user@company.com ownerloginid No User who owns the attendee record.
Doe, Jane ownername No User who owns the attendee record.
Jr. suffix No Max 32 characters.
Manager title No Max 32 characters.
custom_value_1 custom1 No Max 100 characters.
custom_value_2 custom2 No Max 100 characters.
(custom3–custom20) custom3–custom20 No Max 100 characters each.
(custom21–custom25) custom21–custom25 No Max 48 characters each.

More questions about API requirements? Please visit the Concur API site https://developer.concur.com/api-reference/common/attendees/v4.attendees.html.