SocialCrawl

Test your webhooks

Send a test event, catch a real delivery on your machine, and fix the usual failures.

Test a webhook receiver in two steps. First send a signed sample to prove your verifier and parser. Then catch one real delivery and replay it offline.

Send a test event

An event webhook endpoint can be sent a signed sample of any type it subscribes to. The call is free.

cURL
curl -X POST "https://www.socialcrawl.dev/v1/webhook-endpoints/we_V1StGXR8Z5jdHi6BmyT/test" \
  -H "x-api-key: sc_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "type": "discover.completed" }'
Response
{
  "success": true,
  "data": {
    "type": "discover.completed",
    "attempt": {
      "id": "wat_...",
      "delivery_id": "msg_...",
      "test": true,
      "status": 200,
      "outcome": "delivered",
      "duration_ms": 142,
      "response_excerpt": "ok",
      "error": null,
      "created_at": "2026-10-19T10:00:01.000Z"
    },
    "next_step": "The receiver answered 2xx. Real events are delivered the same way, in batches, signed per attempt."
  },
  "credits_used": 0,
  "request_id": "req_..."
}

Leave out type to get the first type the endpoint subscribes to. The sample event carries "test": true and "cursor": null, so your code can tell it apart. A test is sent once and never retried. It does not enter the events feed and does not change the endpoint's health, so a test answered 410 does not disable it.

Monitor, billing, batch and status webhooks have no test call. Use the next section for those.

Test on your machine

A loopback or private URL is refused when you register it, so your receiver needs a public HTTPS hostname. A tunnel works, and so does a hosted request inspector.

  1. Expose your handler on a public HTTPS hostname and register that URL.
  2. Trigger one real delivery you control. For a Monitor, create a throwaway hourly Monitor on a cheap call such as tiktok/profile, and pass your own webhook_secret so a fixture can hold it. For billing, set a low-credit threshold just under your balance and make one billed call.
  3. Capture the raw body and the signature headers. Replay them against your verifier offline, which takes the network out of the loop.
  4. Read what your endpoint answered. Event webhooks list each attempt at GET /v1/webhook-endpoints/{id}/attempts. A Monitor run carries webhook_delivery on GET /v1/monitors/{monitor_id}/runs.
  5. Delete the throwaway Monitor, or pause it, so it stops billing.

Troubleshooting

Next steps

On this page