> For the complete documentation index, see [llms.txt](https://docs.nerovasystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nerovasystems.com/guides/zero-to-live/step-9-webhooks.md).

# Step 9: Webhooks today

What event delivery exists right now, so you design your integration on the surface that is real rather than one that is coming.

{% hint style="info" %}
Requires [Step 8: Bind a channel](/guides/zero-to-live/step-8-channels.md).
{% endhint %}

**Step 9 of 10.** Your tenant is Active and working. This step is different from the others: it documents what event delivery exists right now, so you design your integration on the surface that is real rather than one that is coming.

## 9.1 Current truth

**Experimental.** Webhook endpoint management is live on the `tenant-v1` contract under `/api/v1/tenants/{tenantId}/webhooks` with the `webhook:manage` scope: endpoint CRUD, pause/resume, secret rotation, the event catalog, the delivery ledger with redrive, and per-endpoint test delivery. The delivery contract your receiver implements (the envelope, `Nerova-Signature` verification, the retry schedule) is documented in [Receive events with webhooks](/guides/build-well/webhooks.md), and current surface availability is tracked in [Lifecycle and availability](https://docs.nerovasystems.com/documentation/api/lifecycle).

To try a receiver before real traffic arrives, send a test delivery through the endpoint's own test operation. Test deliveries are signed with the endpoint's real secret and are the only deliveries marked `"livemode": false`.

## 9.2 Design for polling first

Webhooks are Experimental, and even a stable webhook pipeline needs a reconciliation path. Every state this guide has touched is observable by polling, and the idempotent, versioned design makes polling safe and cheap:

* **Provisioning:** poll `GET /api/v1/tenants` for `provisioningState` transitions (step 4.2).
* **Connection health and verification:** re-read the connection and the capability report (steps 5.3 and 6.1).
* **Activation progress:** re-read `GET .../activation/manifest`; it is the authoritative live state machine (step 7.1).
* **Runtime activity:** the work ledger lists what the employee did, each entry carrying stable ids and timestamps you can checkpoint against.
* **Auditing calls:** the request ledger records every API call with its `X-Request-Id`, status, and latency, payloads redacted.

A poll loop that checkpoints on `version` fields and ledger cursors misses nothing that a webhook would have delivered; it only trades latency for simplicity.

## Where you are now

Your integration observes the platform through polling, and you know exactly what eventing is and is not available. Time to prove the whole thing works end to end and go live.

Continue to [Step 10: Go live](/guides/zero-to-live/step-11-go-live.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nerovasystems.com/guides/zero-to-live/step-9-webhooks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.