Webhooks

OutboundSync built KingMinos to answer synchronously — every capability call returns one envelope. Webhooks are the push counterpart: KingMinos emits its own platform events and delivers them, signed, to HTTPS endpoints you register.

What webhooks are for

Today the platform ships one event tranche, Run Health:

• run.failed — a workspace×capability stream transitions healthy→failing (one alert per incident, not per run)
• run.recovered — the same stream is healthy again
• test.ping — a delivery you trigger yourself to prove an endpoint works

If you call KingMinos from Salesforce Flow or a script, you already get errors synchronously. Webhooks are for the rest of your ops stack: get told when enrichment starts failing (with a reason and a remediation), when it recovers, and reconcile anything missed through the events log.

Access

• Webhooks are workspace-scoped. Every /v1/webhooks* and /v1/events route returns 403 webhooks_not_enabled until an OutboundSync admin enables webhooks for your workspace.
• Reads need any workspace-bound key; mutations need the workspace owner.
• At most 20 endpoints per workspace.

Setting up webhooksRegister an endpoint, store the signing secret, URL rules.

Event typesActive run.failed / run.recovered / test.ping, and reserved names.

Payloads and signaturesThe delivery envelope and how to verify KingMinos-Signature.

Delivery and retriesAt-least-once semantics, retry schedule, auto-disable.

Testing and troubleshootingtest.ping, deliveries, replay, and common failures.