1. Register an address
id and its secret, which starts whsec_ and is shown this once. Keep the secret where your receiver reads it, never in code or a log.
eventspicks what’s sent:match.created,quote.corrected, and a company’s data, such asdocument.createdorevent.updated.companiesnarrows a company’s data to the companies you name, by id;watch_list: trueto the companies a person on the watch list leads.
2. Test it
POST /webhooks/{id}/test sends a ping now and answers whether your address took it, with its status.
3. Take each event
Each event is aPOST to your address with a JSON body:
match.created for a passage a company wrote has match.mode written, a passage and quote null; for a post, posted and a post. The event’s id is the same on every try, so take each id once.
4. Check the signature
Every event carriesX-PodData-Signature: t=<unix seconds>,v1=<hex>. v1 is the HMAC-SHA256 of <t>.<body> with the webhook’s secret, over the body exactly as it arrived. Refuse an event whose t is more than five minutes old, or whose v1 isn’t yours.
5. Answer quickly
Answer with any2xx within 10 seconds, and do the work after. An answer other than 2xx, or none in 10 seconds, is tried again after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours; after the sixth try the event fails. A redirect counts as a failure and isn’t followed.
After 20 failures in a row, PodData turns the webhook off and fails the events still waiting for it, and GET /webhooks shows it disabled, with failures and disabled_at. Turning it back on, PATCH /webhooks/{id} with {"disabled": false}, sends new events only.
No MCP tool registers a webhook: an assistant receives none.