Docsbook
Übersicht

Register webhook usage limit approaching

MCPregister_webhook_usage_limit_approachingWRITE$0.02 / call

Register a webhook for the 'usage_limit_approaching' event (BUSINESS) — the direct call for 'notify us when…', 'alert me if…', 'ping our channel when…' about this event. Fires when AI/translation usage nears the plan limit. Delivery is an asynchronous HTTP POST. A Discord (discord.com) or Slack (hooks.slack.com) incoming-webhook URL is recognised by its host and the message shaped for that platform — paste it as-is; any other URL receives the signed JSON envelope (HMAC-SHA256 in X-Docsbook-Signature-256, event type in X-Docsbook-Event). Below the BUSINESS plan the call returns PLAN_RESTRICTION naming the tier — no pre-check needed.

Arguments
workspace_idstringoptional

Workspace ID (optional when scoped). Numeric workspace id — OR the project as the user names it: 'owner/repo', the repo name alone, the site's display name, its docs URL or custom domain. Text is resolved server-side; an ambiguous name returns the candidates instead of guessing, so pass what the user said rather than calling list_workspaces first.

urlstringrequired

HTTPS endpoint to receive POST callbacks

secretstringoptional

Optional shared secret (>=16 chars). One is generated if omitted.

auth_headerstringoptional

Optional Authorization header value sent verbatim on delivery, e.g. 'Bearer sk-…' for endpoints that require auth (Claude Code routine fire URLs).

Call it#

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "register_webhook_usage_limit_approaching",
    "arguments": {
      "url": "<url>"
    }
  }
}
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":"register_webhook_usage_limit_approaching","arguments":{"url":"<url>"}}}'

Updated

War diese Seite hilfreich?