The events you are interested in subscribing toĪt the time of this writing, JW Player offers the ability to subscribe to three events:.An HTTPS endpoint to which we can forward notifications.The properties for which you want to be alerted.The structure of JW Player webhooks is relatively simple, with each webhook having the following properties: JW Player webhooks are managed through a RESTful API. By providing real-time push notifications for media lifecycle transitions, webhooks empower publishers to get their content delivered to their end users faster, and design custom workflows (including through a host of no-code integrations by Zapier, which we recently released and wrote a blog post on).

Webhooks provide our customers a lighter weight and easier-to-maintain solution to address these shortcomings. Until now, customers have had to rely on a pull model to understand the state of their media, an imperfect solution that requires burdensome polling logic, and one which provides an incomplete picture of what has happened, and when. The media lifecycle is asynchronous: the final product, a video you can put on your website, is the result of a series of jobs including, but not limited to, the transcoding of media assets into the various renditions, thumbnail generation, and the indexing of the media asset for distribution via our delivery API’s.

About jw player