> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.pivotal.app/llms.txt.
> For full documentation content, see https://docs.pivotal.app/llms-full.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.pivotal.app/_mcp/server.

# Webhooks

Stream Pivotal events to your own systems. Subscribe to an endpoint, pick the events you care about, and we'll POST a signed payload whenever they happen. Deliveries are retried for 24 hours with exponential backoff.

Outbound delivery runs on [Svix](https://www.svix.com). The signing headers, retry schedule, and verification libraries are the standard Svix ones — drop in any Svix SDK and it works against Pivotal without custom code.

SUBSCRIBE

1. Open **Admin → Developer → Webhooks** in your workspace.
2. Click **Add endpoint**, paste your HTTPS URL, pick the event types to receive.
3. Copy the **signing secret** — Svix shows it once. Store it in your secret manager.
4. Test from the dashboard with **Send test event**. The same UI lists every past delivery with status, payload, and a one-click **Replay**.

WHAT TO READ NEXT

Receive your first event in under five minutes. Local tunnel + signing verification.

The standard shape every payload arrives in. id, type, timestamp, org, data.object.

Node/Express and Python/FastAPI handlers, ready to copy.

HMAC verification in TypeScript and Python.

24h exponential schedule. What counts as success. When delivery gives up.

Fire real events from `pivotal_test_` keys without polluting production data.

EVENT REFERENCE

Fifteen event types ship today, grouped by resource. Each page documents the payload shape, when it fires, a copyable JSON example, and common use cases.

Created, updated, archived, health score dropped, at risk, churned.

Created.

Created, phase changed, state changed, at risk, back on track, launched, completed.

Completed.