This article provides details on the ‘Invitee Substituted into Event Registration’ integration point.
Note
Throughout this document and the product, the term ‘Attendee’ is used interchangeably with ‘Invitee’.
JSON Message Structure
This is an example of the JSON message for this integration point. The data represents the new attendee whom is being substituted in.
{
"eventType": "InviteeSubstitutedInAnEvent",
"messageTime": "2044-04-03T15:46:06.413Z",
"messageStub": "5ddb3c67-e1c9-49b7-8df4-89ce4d921d66",
"message": [
{
"zip": "",
"newContactStub": "33B87EF1-A759-4805-A8C5-271B72434D18",
"city": "",
"address_1": "",
"address_2": "",
"phone_work": "",
"oldContactStub": "DB665428-84D2-4C1D-AF60-2150FCF1B29F",
"last_name": "King",
"visible_on_attendee_list": 1,
"organization_name": "",
"title": "",
"inviteeStub": "82506834-04D3-4C30-971A-DF06EACCD6CD",
"createdDate": "2044-04-03 15:46:06.413",
"registration_code": "LDNXB94RW6Z",
"createdBy": "(Cvent - hlee) Hlee",
"eventStub": "0B4C4410-1D46-43CD-A903-E8CF9DE6ADE5",
"remote_avatar_url": "",
"accountStub": "C4AD3933-0FED-4379-B602-CB56B1D832C5",
"state": "",
"first_name": "Ronald",
"email": "example@test.com"
}
]
}
Understanding the JSON Message
- Empty Fields: Fields appearing as empty (
""
) indicate no data is available for that field. - Field Order: The sequence of fields in the payload is not fixed and may vary.
Last updated on