Scenario

It's the generation of instant gratification- don't you love it when that LinkedIn post you worked really hard on starts getting traction? Well, summits are hard work, and it's only natural that you want to know how well it's doing from the minute it goes 'live'.

A webhook is a way for the HeySummit API to provide information about some specific actions occurring in your event. Webhooks deliver information in real-time, so you get an immediate notification once something happens in your summit- for instance when you've got a new sign-up.

Currently, we only support outgoing webhooks. What that means is that HeySummit is able to send info from HeySummit, outwards.

For example, you could configure HeySummit to send an outgoing webhook for a new registration, and then have that webhook send that information into Slack to notify you (via a notification on your device) of any new summit activity.
 
More of a visual learner? Check out our video: 
Note that we recently changed how we refer to our webhooks.
  • "Ticket Purchased" is now "Checkout complete"

  • "New Attendee" is now "Attendee registration started"

  • "New Talk Attendee" is now "Talk added to attendee schedule"

 

What kind of data will I receive and when will the webhooks be fired?

Currently, we provide 3 webhooks:

  1. Attendee registration started:

    An attendee is created as soon a user submits their email into a call to action box. This can happen at the beginning of the registration process, or further down the line. Because of the different entry points, you may receive varied data. If they entered it as their first step, you might only receive their email address. If they enter it later down the line, you may receive more. 

    Think of this webhook as a “someone has signaled interest in my event, and they’ve begun the registration process” flag.

  2. Checkout complete:

    This webhook is triggered when an attendee completes the registration/checkout process. Because this only sends at the very end of the registration process, you are guaranteed the attendee’s complete registration information.

    This webhook is useful if you want a consistent attendee data payload, and are only interested in knowing about attendees who complete the registration process to secure a ticket.

  3. Talk added to attendee schedule:

    This webhook will let you know anytime an attendee signs up for a talk/session. It will fire for every sign up, which means that if an attendee signs up for two sessions, you would receive two payloads for that attendee. 

    This webhook is useful if you want to keep an eye on how popular certain sessions are or want to see when people are signing up.

Quick start

Let's walk you through the process that will have your outgoing webhooks set up in a jiffy :
  1. Make sure you have a live URL that will receive the HTTP POST with the data.
  2. Go to Event Setup > Webhooks and click on Add Webhook.
  3. Choose the Action in the drop-down menu, Attendee registration started, Checkout complete or Talk added to attendee schedule.
  4. Enter your full URL. Don't forget to hit Save!
Webhooks are constructed as an HTTP request with the following composition:
  • Sent via the POST method.
  • Application/JSON mime type defined in the headers.
  • Valid JSON payload.
Note: If we're unable to receive a status code from your URL. We will retry every 15 minutes, for up to 3 attempts.
Please note that we cannot offer support for the setup of webhooks on the Event Organizer's side. If you require technical support for setting up the receiving side of the webhook, we advise consulting with a developer