Manage Stora webhook endpoints programmatically and subscribe to lifecycle events across contracts, invoices, and units
domain: docs.stora.co · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate to the Stora Public API using an access token or OAuth 2.0 per Stora's Authentication guide.
Create a webhook endpoint with the create-a-webhook-endpoint call, specifying your HTTPS receiving URL and the event types to subscribe to.
List existing endpoints with list-all-webhook-endpoints, and fetch one by ID with show-a-webhook-endpoint.
Toggle delivery with enable-a-webhook-endpoint / disable-a-webhook-endpoint rather than deleting and recreating.
Subscribe to event types such as contract.signed, invoice.paid, subscription.cancelled, and unit.overlocked/unit.repossessed to drive downstream automations.
Remove an endpoint you no longer need with delete-a-webhook-endpoint.
Known gotchas
Stora's webhook catalog spans 40+ typed events across contacts, deals, invoices, units, and tasks — subscribe narrowly to what you actually consume.
deal.stage_changed also fires alongside deal.created for a deal's very first stage — dedupe if you only care about true stage transitions.
The Public API webhook-endpoints resource is the code-first path; Stora also offers a separate Zapier-based no-code webhook automation — don't build both against the same downstream system without reconciling.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?