Revolv3 Webhooks

generated: '2026-10-26'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.revolv3.com/docs/webhook-events/webhook.md
sources:
- https://docs.revolv3.com/docs/webhook-events/webhook.md
- https://docs.revolv3.com/docs/webhook-events/creating-a-webhook.md
- https://docs.revolv3.com/docs/webhook-events/webhook
- https://docs.revolv3.com/docs/webhook-events/creating-a-webhook
description: Revolv3 provides webhooks for real‑time event notifications.
events:
- event: SubscriptionCreated
  description: Sent when a subscription is successfully created and becomes active.
- event: SubscriptionChanged
  description: Sent when an existing subscription is updated.
- event: InvoiceCreated
  description: Sent when a new invoice is created and ready for payment.
- event: InvoiceStatusChanged
  description: Sent when an invoice’s status changes (e.g., payment succeeded or failed).
- event: InvoiceAttemptCreated
  description: Sent when a payment attempt is made.
- event: InvoiceAttemptStatusChanged
  description: Sent when a payment attempt’s status changes (e.g., approved or declined).
- event: WebhookTest
  description: Sent during webhook setup to verify the endpoint works.
delivery:
  signature: x-revolv3-signature header containing a Base64‑encoded HMAC‑SHA256 hash
  content_type: application/json (payload includes a `Body` JSON string and an `Entropy` string)​
note: Signature is generated by concatenating the webhook URL, a `$` character, and the raw request body, then applying HMAC‑SHA256 with the webhook
  key and Base64‑encoding the result. The endpoint must respond with HTTP 200 OK. No retry policy is documented on the pages, so retry information
  is absent.
docs: https://docs.revolv3.com/docs/webhook-events/webhook.md