Webhooks

Webhooks allow your application to receive real-time notifications about events that occur in your Billingrails application. By setting up webhooks you can:

• Keep your application in sync with Billingrails
• Sync information with other third-party services that your business uses
• Set up automation workflows based on specific events

Core concepts

Webhook events

Webhook events are specific occurrences within your Billingrails account that can trigger a webhook notification. Examples of webhook events include:

• Customer created
• Subscription updated
• Invoice paid
• Payment failed
• Refund issued

Webhook destinations

A webhook destination is the URL endpoint where webhook notifications are sent. This is typically an endpoint in your application that is set up to receive and process webhook payloads.

Webhook signatures

To ensure the security and authenticity of webhook notifications, Billingrails uses HMAC signatures. Each webhook payload is signed using a secret key that you provide when setting up the webhook. Your application can then verify the signature to confirm that the payload was sent by Billingrails and has not been tampered with.