Webhooks
Receive signed, durable event notifications and trigger reliable agent workflows from Quire changes.
Last updated
Webhooks notify an HTTPS endpoint when selected Quire resources change. They are designed for event-driven agent loops: receive metadata, decide whether to act, then use MCP to read current content and perform authorized work.
What a webhook contains
Every delivery has stable event and delivery IDs, subscription scope, team identity, contributing actors, a timestamp, and event-specific resource metadata. Document events contain IDs, .md paths, changed fields, and relevant previous values.
Webhook bodies never contain document Markdown or raw Yjs collaborative-editor deltas. Your consumer fetches current content through MCP when the event requires it.
Delivery guarantees
Delivery is at least once, with no global ordering guarantee. Verify every signature over the untouched request bytes and deduplicate with the delivery or event ID. Quire retries transient failures and keeps delivery history for 30 days.
Return a 2xx response only after the notification is durably accepted. Process long-running agent work asynchronously so the webhook endpoint can respond quickly.