> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zivio.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhooks Overview

> Receive real-time notifications when things happen in Zivio

### 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 HTTP `POST` 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](/api-reference) endpoint.

<Tip>Webhooks are ideal for keeping an external system — such as an ERP, finance tool, or data warehouse — in sync with Zivio in near real time.</Tip>

### How it works

<Steps>
  <Step title="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.
  </Step>

  <Step title="An event occurs">
    Something happens in Zivio that matches one of your subscribed events — for example, an invoice is paid.
  </Step>

  <Step title="Zivio sends a request">
    Zivio sends a signed `POST` request containing a JSON payload to your URL.
  </Step>

  <Step title="Your endpoint responds">
    Your endpoint verifies the signature, processes the event, and returns a `2xx` response to confirm receipt.
  </Step>
</Steps>

### Key concepts

<ResponseField name="Event" type="">
  An action that happens in Zivio, such as `invoice.created` or `offer.accepted`. See the full list in [Event Types](/webhooks/event-types).
</ResponseField>

<ResponseField name="Webhook" type="">
  A destination you configure to receive events: a URL, a description, and the set of events it is subscribed to.
</ResponseField>

<ResponseField name="Delivery" type="">
  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.
</ResponseField>

<ResponseField name="Signing secret" type="">
  A secret unique to each webhook, used to sign every request so you can verify it genuinely came from Zivio.
</ResponseField>

### Built on an open standard

Zivio webhooks follow the [Standard Webhooks](https://www.standardwebhooks.com/) 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

<CardGroup cols={2}>
  <Card title="Get Started" icon="play" href="/webhooks/getting-started">
    Create and manage your first webhook.
  </Card>

  <Card title="Event Types" icon="list" href="/webhooks/event-types">
    Browse every event you can subscribe to.
  </Card>

  <Card title="Payloads" icon="code" href="/webhooks/payloads">
    Understand the structure of a webhook request.
  </Card>

  <Card title="Verifying Signatures" icon="shield-check" href="/webhooks/verifying-signatures">
    Confirm that requests really come from Zivio.
  </Card>
</CardGroup>