Skip to content
WebsitePlatform

Reply to the sender

Answer each webhook with your own JSON, text or XML body.

A custom reply is the response body Hookspot returns to the service that sends your webhook. Set one on the Docs demo source from the quickstart, then check it with curl.

  1. Open Routes, click the Docs demo card and click Open.
  2. Under Reply to sender, click Customize.
  3. Check Send a custom reply to the sender.
  4. Keep JSON as the Reply content type.
  5. Enter {"accepted":true} as the Reply body.
  6. Click Save.
Saved Docs demo settings with Send a custom reply to the sender checked, JSON selected and accepted set to true in Reply body.

The reply changes only what the sender gets back. Your app still gets the webhook as it arrived.

If the body is not valid JSON or XML, the form shows invalid json or invalid xml and keeps the old settings.

On the source’s Overview, copy the curl command beside its webhook URL. Run it in any directory to see your custom reply:

curl <webhook-url> -H 'content-type: application/json' --data-raw '{"type":"hookspot.test"}'
{"accepted":true}

Hookspot still stores the request and forwards it to your app. Under Reply to sender, the source’s Overview shows the reply it sends now.

Pick the Reply content type that matches your Reply body: JSON, TEXT or XML. The sender gets the body with that content type.

The status is always 200, and you cannot add headers. A rejected request gets the reply too, unless it failed verification. Then Hookspot answers 401.

Hookspot sends the reply only after it stores the request. Otherwise the sender gets another answer from Responses, such as 429 or 503.

  1. Open the source’s Settings.
  2. Uncheck Send a custom reply to the sender.
  3. Click Save.

Hookspot deletes your reply body and answers with {"status":"ok","request_id":"req_…"} again.