This article provides details on the ‘Meeting Request Submitted’ integration point.

JSON Message Structure

This is an example of the JSON message for this integration point. The data represents a submitted meeting request.

{
  "eventType": "MeetingRequestSubmitted",
  "messageTime": "2044-01-23T03:42:59.253Z",
  "messageStub": "13bb9bf3-fb71-49ca-9dbe-c30b472ae9f0",
  "message": [
    {
      "requestor_work_phone": "555-555-5555",
      "evt_stub": "F369A3FA-D6F2-4B54-96E0-E57582E495C4",
      "smm_form_stub": "08D80DFE-BF9E-443B-AD5B-6992898090DE",
      "meeting_request_name": "Companywide",
      "requestor_last_name": "Evelynn",
      "requestor_first_name": "Smith",
      "requestor_email_addr": "test@example.com",
      "last_modified_date": "1547005379253",
      "accountStub": "0C8B412B-EB8E-41DA-8974-C403D888B907",
      "created_date": "1547005379067",
      "meeting_request_event": {
        "evt_start_date": "1548912660000",
        "evt_end_date": "1548998940000"
      },
      "meeting_request_stub": "DEC4643A-40E8-4CB0-A1B4-1A07BA037354"
    }
  ]
}

Understanding the JSON Message

  • Empty Fields: Fields appearing as empty ("") indicate no data is available for that field.
Last updated on