What are Webhooks?
Webhooks let Zivio notify your systems automatically the moment something happens on your platform — a new invoice is created, an offer is accepted, a milestone is approved, and more. Instead of repeatedly calling the API to check for changes (polling), you give Zivio a URL and we send an HTTPPOST request to it whenever a relevant event occurs.
Each notification (a “delivery”) contains a JSON payload describing what happened, including the same data you would receive from the equivalent API Reference endpoint.
How it works
Create a webhook
In your Zivio platform, you create a webhook by providing a destination URL and choosing which events you want to be notified about.
An event occurs
Something happens in Zivio that matches one of your subscribed events — for example, an invoice is paid.
Key concepts
Event
An action that happens in Zivio, such as
invoice.created or offer.accepted. See the full list in Event Types.Webhook
A destination you configure to receive events: a URL, a description, and the set of events it is subscribed to.
Delivery
A single attempt to send one event to your URL. Deliveries are signed, automatically retried on failure, and recorded in a delivery log you can review.
Signing secret
A secret unique to each webhook, used to sign every request so you can verify it genuinely came from Zivio.
Built on an open standard
Zivio webhooks follow the Standard Webhooks specification. This means signatures and headers are compatible with a wide range of open-source libraries, so verifying and consuming events is straightforward in most languages.Next steps
Get Started
Create and manage your first webhook.
Event Types
Browse every event you can subscribe to.
Payloads
Understand the structure of a webhook request.
Verifying Signatures
Confirm that requests really come from Zivio.

