Developer DocumentationWebhooksJSON MessagesAttendee EmailsInvitee/Guest Email Bounces

This article provides details on the ‘Invitee/Guest Email Bounces’ 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 attendee that was sent an email.

{
   "eventType":"InviteeOrGuestEmailBounced",
   "messageTime":"“2044-04-25T11":"03":12.350Z”,
   "messageStub":9e037662-0911-4338-9bf4-e61ea731fc05,
   "message":[
      {
         "workStateCode":"",
         "isGuest":false,
         "prefix":"",
         "workZipcode":"",
         "contactType":"",
         "updatedDate":2016-04-25,
         "workCity":"",
         "homeCity":"",
         "registrationDate":2016-04-25,
         "homeZipcode":"",
         "homeFax":"",
         "nickName":"",
         "homePhone":"",
         "workFax":"",
         "workAddress1":"",
         "workAddress2":"",
         "firstName":"Paul",
         "workAddress3":"",
         "confirmationNumber":“F9NG768637N”,
         "mobilePhone":"",
         "responseMethod":"Planner-Responded",
         "eventStub":“C8CFF23F-4A1E-419C-8E11-C9AC34FC1A0A”,
         "designation":"",
         "homeCountry":"",
         "lastName":"Bruce",
         "eligibleCredits":0.00,
         "gender":"",
         "customFields":[
            {
               "id":81AD013C-2EE9-417E-9562-D440F44D2BBA”,
               "name":"Date Hired",
               "value":""
            },
            {
               "id":8E94CED1-4B82-4E3F-A16A-15C2FFB98300,
               "name":"Company ID",
               "value":""
            },
            {
               "id":490E2A8D-5B3A-402E-A14B-7C9517030C8A”,
               "name":"Department",
               "value":""
            }
         ],
         "workCountry":"",
         "title":"",
         "homeStateCode":"",
         "referenceId":"",
         "optedOut":"yes",
         "totalCredits":0.00,
         "workState":"",
         "company":"",
         "participantStatus":true,
         "registrationPath":"Registration Option",
         "accountStub":“B1698375-E931-4E45-AEC7-FFD3D6CD451F”,
         "email":"test@example.com",
         "ccEmail":"",
         "visibleOnAttendeeList":1,
         "fullName":"Paul Bruce",
         "dateOfBirth":"",
         "homeState":"",
         "inviteeStub":“B3742AB1-0588-4F35-96E4-4F0811491D11,
         "invitationBy":"Planner-Invited",
         "homeAddress3":"",
         "homeAddress2":"",
         "unsubscribed":"no",
         "homeAddress1":"",
         "inviteeStatus":"Cancelled",
         "internalNote":"",
         "middleName":"",
         "workPhone":""
      }
   ]
}

Understanding the JSON Message

  • Arrays: The customFields array is dynamic; it changes over time as planners add or remove custom fields.
  • Empty Fields: Fields appearing as empty ("") indicate no data is available for that field.
Last updated on