Image
Webhooks

Many organizations automate their internal processes to achieve greater efficiency. For example, an engineering team may wish to automatically generate a new video conferencing Meeting ID when an incident or outage occurs on the production servers. Why? So that all parties who are responsible for keeping the production servers intact are able to remain in sync regarding  the  outage and have confidence that a virtual meeting will be automatically available to join for troubleshooting or to get the latest updates. Additionally, team leaders may want to track the individuals who joined those meetings and who did not, so that they can send a follow-up notification via SMS/Slack/email to people who didn’t attend the meeting to ensure everyone remains informed. 

More video conferencing examples can be sourced from developers who are integrating one of the BlueJeans SDKs into their apps or websites.   Oftentimes, these developers need to understand what specific time a meeting started and whether the meeting host was available when an attendee joined the meeting.  Similarly, when a meeting ends, the developer may also be interested in knowing when a meeting recording is made available for download, so they add it to their cloud or local storage.  

Introducing BlueJeans Webhooks

Via BlueJeans Webhooks, developers can now listen for important events that are occurring across your BlueJeans Meetings instance.  Events that occur before, during, and after the meeting are sent via a POST API call to your webhook server to trigger automation of the next actions that you plan to implement in your app/website.

The flow diagram below demonstrates how a typical scenario (user joining a meeting) is mapped out with BlueJeans Webhooks. 

Image
webhook3

BlueJeans has designed our Webhooks to be: 

Easy to Configure
Follow these simple steps to configure your webhook server via the BlueJeans admin panel.

Secure & Trustable
BlueJeans expects your webhooks server to return the secret key when a validate call is made. 

This certifies that the receiver is a trustable entity. With every POST call, BlueJeans sends an Authorization header which includes a JWT signed key. You can use the public key to verify that the event was sent by BlueJeans. More details can be referred to here.

BlueJeans also provides you ample amount of time to bring back your webhook server in case it goes down due for any reason. More details here.

Easy to Integrate

On successful validation and selection of events that you are interested in, BlueJeans starts sending events to your webhook server within a few minutes. 

Use BlueJeans Webhooks to fully automate your internal and/or product processes. Experience our best-in-class developer platform to help scale your product and make your processes more efficient.

To learn more about the BlueJeans Developer Platform, please click here.