Real-time event-driven screens. Webhook-powered updates.
Trigger instant content changes on your screens by sending a webhook to Hangar.Media. Receive webhooks when screen events happen. Build real-time, event-driven digital signage workflows without polling or delays.
Instant screen updates triggered by real-world events
Webhooks eliminate the delay of polling-based integrations. When an event happens in your external system, it sends an HTTP POST to Hangar.Media and your screens update within a second. Conversely, when something happens on your screens, Hangar.Media can notify your systems instantly. This bidirectional webhook support makes your digital signage a real-time participant in your operational workflows.
What you can do with Webhook-powered updates.
Three capabilities that make this integration essential for your digital signage network.
External events control your screens
Set up inbound webhook endpoints in Hangar.Media that listen for HTTP POST requests from your external systems. When a webhook arrives, it triggers a predefined action on your screens such as content push, playlist switch, alert display, or data update.
One HTTP request, instant screen reaction.
Custom webhook URLs for different trigger types
JSON payload parsing with field mapping
Multiple actions per webhook for complex responses
Your screens notify your systems
Set up Hangar.Media to send webhooks to your systems when screen events happen. Get notified when a player goes offline, content finishes playing, or a schedule changes. Use these notifications to trigger workflows in your monitoring, billing, or operational systems.
Your systems stay informed about every screen event.
Player status change notifications
Content play completion events
Schedule and playlist change alerts
Verified and authenticated webhook delivery
Every webhook includes an HMAC signature that you can verify to ensure it came from a trusted source and was not tampered with in transit. Inbound webhooks can require authentication tokens, IP whitelisting, or both to prevent unauthorized triggers.
Secure by default so you can trust every webhook.
HMAC-SHA256 signature on all outbound webhooks
Token-based authentication for inbound webhooks
IP whitelisting for additional inbound security
Four steps to connected screens.
From setup to live content in minutes, not days.
Create a webhook endpoint
Set up an inbound webhook URL in Hangar.Media and define what action it triggers. Copy the generated URL and authentication token.
Set up your external system
Add the Hangar.Media webhook URL to your external system as a notification endpoint. Include the authentication token in the request header.
Map payload data
Define how incoming webhook data maps to screen content. Map JSON fields to template variables, alert text, or playlist identifiers.
Test and activate
Send a test webhook from your external system and verify the screen responds correctly. Enable the webhook for production use.
Built for every sector.
See how different industries use this integration to drive results.
Emergency alert triggers
Trigger emergency alerts on all hospital screens instantly via webhook when the emergency management system detects a critical event.
CorporateMeeting room status updates
Update meeting room door screens in real time via webhooks from your calendar system when meetings start, end, or are cancelled.
RetailFlash sale activation
Trigger promotional content on all store screens instantly via webhook when your marketing team launches a flash sale from the e-commerce platform.
PublicTransit delay notifications
Push real-time service disruption messages to transit station screens via webhook from the operations control centre.
Common questions. Straight answers.
What is the difference between webhooks and the REST API
Webhooks are event-driven and push-based. Your external system sends a request to Hangar.Media when something happens. The REST API is request-driven and pull-based. Your application calls the API when it needs to do something. Webhooks are faster for real-time triggers. The REST API is better for complex operations and data retrieval.
How many inbound webhooks can I set up
There is no limit on the number of inbound webhook endpoints you can create. Each endpoint has its own URL, authentication token, and action setup. You can create as many as your workflow requires.
What happens if a webhook fails to deliver
For outbound webhooks, Hangar.Media retries failed deliveries up to five times with exponential backoff. Failed deliveries are logged in the webhook history. For inbound webhooks, the sending system is responsible for retry logic. Hangar.Media returns appropriate HTTP status codes so your system can handle retries.
Can I test webhooks without affecting live screens
Yes. You can target webhook actions to test screens or sandbox environments. Hangar.Media also includes a webhook testing tool that simulates inbound webhooks and shows you the resulting action without executing it on any screen.
One price. The whole platform.
That's how we think signage should work. Content editor, screen management, and 200+ app integrations — all included from day one.