<img height="1" width="1" src="https://www.facebook.com/tr?id=1501109533686083&amp;ev=PageView &amp;noscript=1">
Skip to content
English
Sign in
Contact us
  • There are no suggestions because the search field is empty.

Understanding and Setting Up Webhooks

Webhooks are a powerful tool for integrating Resova with external systems by automatically sending real-time data when specific events occur in your account. This ensures that your systems remain synchronized and responsive without manual intervention.

How Webhooks Work

When specific events occur in Resova, data related to those events (e.g., transaction, booking, or block details) is sent to a designated webhook URL in real time. This enables seamless communication between Resova and your external systems.

Available Events

You can configure webhooks for the following seven events:

  • transaction.created: Triggered when a new transaction is created.
  • transaction.cancelled: Triggered when a transaction is canceled.
  • booking.updated: Triggered when a booking is updated.
  • booking.cancelled: Triggered when a booking is canceled.
  • block.created: Triggered when a block is created.
  • block.updated: Triggered when a block is updated.
  • block.cancelled: Triggered when a block is canceled.

Accessing Webhook Settings

  1. Navigate to Settings > General Settings > Webhooks in the Resova Admin dashboard.
  2. Click + Add Endpoint to create a new webhook.

Creating and Managing Webhooks

  • Add Endpoint: Enter the URL of the external system where Resova will send event data.
  • Configure Events: Select the events you want to trigger this webhook.
  • Enable or Disable: Use the toggle to activate or deactivate specific endpoints.
  • Delete: Remove endpoints that are no longer needed.

Best Practices

  1. Secure Your URL: Ensure the endpoint URL uses HTTPS for secure data transmission.
  2. Validate Incoming Data: Implement server-side validation to confirm data integrity and authenticity.
  3. Test Webhooks: Use a test URL to verify event payloads and ensure proper integration.
  4. Monitor Logs: Keep an eye on your system logs for successful and failed webhook attempts.