scrapewise_update_group_delivery_webhook
Creates (or changes) the group's webhook: Scrapewise POSTs a signed JSON body to your https URL when the
daily matched file is ready (FILE_READY) and when the day turns COMPLETE, PARTIAL or STALE (DAY_COMPLETE,
DAY_PARTIAL, DAY_STALE; the body is the delivery-status document). Each state fires once per day and
matching run. Delivery is at least once: de-duplicate on the X-Scrapewise-Delivery header; events can
arrive out of order - keep the newest computedAt. Failed deliveries are retried after 1 m, 5 m, 30 m,
2 h, 6 h; after many dead deliveries in a row the webhook switches itself off.
Signature: X-Scrapewise-Signature: v1=<hex HMAC-SHA256(secret, "<X-Scrapewise-Timestamp>.<raw body>")>.
The secret is answered ONLY by the call that creates the webhook - store it then. To change the secret:
delete the webhook, then create it again. Changing url / events / enabled keeps the secret.
Args:
- id (string, path, required): the group's id (you must own the group).
- body (object, required): {url: "https://...", events?: [FILE_READY, DAY_COMPLETE, DAY_PARTIAL,
DAY_STALE] (default all four), enabled?: true}. The url must be https, on the public internet, at most
2,048 characters, with no user:password.
- customerRef (string, query, optional): admin keys in Take Over only.
Returns:
{url, events, enabled, createdAt, lastDeliveryAt, lastStatus, lastHttpStatus, autoDisabledAt, secret}
- secret only when the webhook was just created.
Examples:
- Use when: "notify https://example.com/hooks/scrapewise when today's data for group {id} is complete".
- Use when: switching a webhook back on after it switched itself off (enabled: true).
- Don't use when: you only want to look at the status -> get the group delivery status.
Error Handling:
- 400 WEBHOOK_URL_REFUSED: not https, private / local address, unknown host, credentials in the url.
- 400 WEBHOOK_INVALID: unknown event. 403 WEBHOOK_OWNER_ONLY: the group is shared with you.
- 503 WEBHOOK_UNAVAILABLE: webhooks are not available on this server right now (status still works).
- 409 TAKE_OVER_ACTIVE; 401 Unauthorized; 500 INTERNAL.[runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP outputSchema is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>",
"body": "<body>"
},
"name": "scrapewise_update_group_delivery_webhook"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the group's id (you must own the group). | |
| body | Yes | The webhook: an https URL, the events to send, on/off. | |
| customerRef | No | Admin keys in Take Over only: the customerUniqueRef of the customer the admin works for. Required then; leave it out otherwise. |