Unregister webhook
unregister_webhookWRITE$0.02 / callRemove a webhook by its id (Free). Caller must own the workspace. BEFORE ARMING THIS, call docsbook_expert with what you are trying to catch: it names what is worth watching and at what threshold. An alert that fires on noise is muted within a week, which is worse than no alert. One call, changes nothing.
Webhook id (from list_webhooks).
Call it#
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "unregister_webhook",
"arguments": {
"webhook_id": 0
}
}
}curl -X POST 'https://docsbook.io/api/mcp/server' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"unregister_webhook","arguments":{"webhook_id":0}}}'Try it over REST#
The same tool is callable as a plain HTTP request, no MCP client required. It runs on the same server, at the same price.
Your workspace is resolved from the API key, so workspace_id is decided server-side here and anything you send for it is ignored.
/api/v1/tools/unregister_webhookYour API key, sent as Authorization: Bearer dbk_YOUR_API_KEY.Sent as the Authorization header. Your key is used only by your browser for this request — it is never sent to Docsbook or stored.
The arguments above, as one JSON object.
curl -X POST 'https://docsbook.io/api/v1/tools/unregister_webhook' \
-H 'Authorization: Bearer dbk_YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{"args":{"webhook_id":0}}'