The registration.submitted webhook event is sent when a registration is received for a chat event in your account. This enables you to immediately record the registration in your application or systems instead of getting registrations from the Brazen API by polling or at the end of an event.

Request Payload

The payload object in the webhook request contains the event registration representation as described in the registrations resource.

Here's an example:

{
  "secret" : "v2q910nklaldr73w2",
  "event" : "registration.submitted",
  "timestamp" : "2016-02-02T18:04:27Z",
  "payload" : {
    "id": 783942,
    "first_name": "Han",
    "last_name": "Solo",
    "email": "[email protected]",
    "user_id": 723913,
    "external_id": "hansolo2392",
    "verified_user": true,
    "registered_on": "2016-02-02T18:04:26Z",
    "last_updated": "2016-02-02T18:04:26Z",
    "event_code": "7pq6smend",
    "peer_group": "candidates",
    "data": "field1label=value&field2label=value"
  }
}

See the Brazen standard webhook request schema for more information on how a payload is expressed in a request.

Response

Your webhook must respond with a HTTP success status code (2xx) such as 200 OK or 202 Accepted to signal that the call was successful. When Brazen receives a redirection (3xx), client error (4xx), or server error (5xx) status code, Brazen will record the call did not succeed, but will not retry the call. The response body can be empty.

HTTP/1.1 200 OK
Date: 29 Mar 2016 04:36:25 GMT
Content-Type: text/plain; charset=UTF-8
Cache-Control: no-cache
Pragma: no-cache
Content-Length: 0