# Webhooks in Runmerge

# Introduction

Webhooks in Runmerge provide a seamless way for Eventtech platforms to receive real-time updates without needing to poll APIs continuously. By subscribing to specific events, organizations can ensure their systems stay synchronized with Runmerge’s event data model, reducing overhead and improving efficiency.

# Why Use Webhooks?

Real-time Updates: Receive instant notifications when critical actions occur.
Reduced API Load: Avoid the need for frequent polling, saving bandwidth and compute resources.
Seamless Integrations: Automatically trigger workflows in third-party systems based on event updates.
Scalability: Handle thousands of events efficiently as your business grows.

# Webhook Use Cases in Runmerge

Webhooks can be used in various scenarios, including:

Sync Completion Notifications: Get notified once Runmerge completes a full sync, ensuring your system processes only finalized data.
New Record Creation: Trigger actions when new entities such as events, sessions, attendees, or tickets are added to the system.
Entity Updates: Detect and process updates to existing records, such as changes in attendee details, session schedules, or ticket availability.
Deletion Alerts: Ensure systems remain consistent by handling notifications when records are deleted.
Data Pipeline Feeds: Stream Runmerge data into external warehouses or analytics systems in real-time.
Automated Business Logic: Trigger workflows like sending confirmation emails, updating CRM records, or notifying stakeholders when key changes happen.

# What You Get After Subscribing

Once a system subscribes to Runmerge webhooks, it can receive notifications for key events, such as:

Sync Completion: Notifies when a data sync has successfully completed.
Entity Updates: Alerts when attendee, session, ticket, or other entities are updated.
New Record Creation: Triggered when new data (e.g., an event, session, or speaker) is created.
Deletion Events: Get notified when a record is removed from Runmerge.
Error Handling Alerts: Receive notifications if an issue occurs during a sync process.
New connection creation: Receive notifications when a new integration or connection is successfully established in Runmerge.

# Security and Reliability

Runmerge ensures webhook security and reliability through:

Signature Verification: Each webhook payload is signed using HMAC with SHA-256 to verify authenticity and prevent tampering.
HTTPS Enforcement: Webhook endpoints must use HTTPS to ensure secure data transmission.
Retries on Failure: If a webhook endpoint fails to respond, Runmerge retries delivery with exponential backoff, ensuring event delivery even during temporary outages.
Customizable Event Subscriptions: Organizations can selectively subscribe to specific events to receive only relevant notifications, reducing unnecessary processing.
Logging and Monitoring: Failed deliveries are logged, and organizations can access webhook logs via the dashboard to diagnose issues.

# Conclusion

Webhooks are a powerful tool within Runmerge, enabling real-time data synchronization and automation while minimizing API usage. By leveraging webhooks, organizations can ensure their systems remain up-to-date and responsive to changes in the event landscape.