Outbound webhooks

A webhook lets your other tools hear about what happens in Domino as it happens. You give Domino a web address, pick the events you care about, and Domino sends a signed message there each time one occurs. For example:

• Post in your team's Slack when a member completes a quest.
• Add a qualified referral to your CRM.
• Ship merch when a member earns a prize.

Each endpoint belongs to one project and environment. Creating one doesn't send earlier activity.

An event says what happened, not who made it happen: it names no operator, and no tool such as the CLI, Console or an AI assistant connected through Domino's MCP server. The project's audit history records the operator.

Events and deliveries

An event describes one change, such as a completed quest. A delivery is one endpoint's attempt to send that event, including its automatic retries. Replaying a finished delivery sends the same event again, with its original ID and body.

• The same event can arrive twice. Delivery is at least once: a timeout can happen after your receiver accepted a request. Each event has an ID, so your receiver can spot a repeat.
• Order isn't guaranteed, even for the same member. When it matters, read the current state through the management API.
• Completed doesn't mean delivered. A completed quest doesn't mean its Discord role or prize has arrived. completion.created and reward.delivery.failed describe different changes.

Scope and recovery

Test and live have separate endpoints, signing secrets, subscriptions, and delivery logs. Both send real requests, so point a test endpoint at a test receiver.

If deliveries keep failing, Domino turns the endpoint off. In Console Settings → Webhooks you can see why, fix your receiver, turn the endpoint back on, and replay the deliveries Domino kept.

See Receive outbound webhooks to configure a receiver and Webhook reference for events, permissions, and limits.

Delete an endpoint

Choose Delete endpoint in Console Settings → Webhooks and give a reason. Deleting stops new deliveries and retries and frees up room for another endpoint. Its delivery history stays, read-only, under Deleted endpoints. A deleted endpoint can't be turned back on, rotated or replayed; create a new one to send again.