Brazen Developer Resources

Brazen Developer Resources

Welcome to the hub for Brazen developer tools! We've moved to a new home, but you'll still find all the same comprehensive guides and API reference documentation to help you start integrating with Brazen as quickly as possible. These guides contain step-by-step instructions on how to set up Brazen integrations, including custom registration experiences through SSO and our API, syncing data with outgoing webhooks, importing job postings with job feeds, and connecting with other enterprise applications. If you get stuck, help is always an email away at developers@brazen.com. Let's build something cool!

Get Started    API Reference

Event: registration.submitted

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": "2819c2237f76453a919d413861904646",
    "user_id": 723913,
    "external_id": "hansolo2392",
    "email": "han@theresistance.org",
    "registered_on": "2016-01-08T12:14:32Z",
    "last_updated": "2016-01-08T12:14:35Z",
    "data": "field1label=value&field2label=value",
    "event_code": "7pq6smend"
  }
}

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 request 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

Event: registration.submitted


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.