Webhooks

Hosted writes can POST a signed event to HTTPS endpoints you register on the dashboard. Webhook setup is dashboard-only. It is not an MCP tool. BYO does not send these webhooks to Bootstrapware. Your adapter returns events to the widget, and you may notify from your own server.

• comments.thread_created
• comments.comment_created
• comments.comment_updated
• comments.comment_deleted
• comments.thread_resolved
• comments.thread_reopened
• comments.user_mentioned

Schema version is 1. The envelope is event, workspaceId, productId (comments), timestamp, and data. data contains eventId, schemaVersion, appId, environment, tenantKey, resourceType, resourceId, threadId, actorId, occurredAt, plus commentId when the event is about a comment, plus mentionedUserId on comments.user_mentioned. No body, display name, resource title, or email.

createThread writes comments.thread_created, comments.comment_created, and any mention events in one transaction. reply writes comments.comment_created plus mention events. markRead has no event. A replay does not POST again.

The signature is HMAC-SHA256 hex of the raw body in X-Bootstrapware-Signature. Timeout is 5000 ms. One retry runs after 400 ms. A failed POST can leave a committed event undelivered. Dedupe on eventId. This is not exactly-once HTTP delivery, and it is not an email. Your server fetches content only after it authorizes the recipient. Guide: notification callbacks.

Related: Mentions · Privacy by mode · API overview