moqapi.dev_
/docs
Home

Webhook Receivers — Catch, Inspect & Replay Incoming Webhooks

Webhook receivers let you create endpoints that capture and inspect inbound HTTP requests from external services. Debug webhook payloads from Stripe, GitHub, Twilio, or any service that sends webhooks.

01 — How It Works

  1. Create a Receiver — Go to Webhooks → Receive Webhooks → Create Receiver.
  2. Copy the URL — Each receiver gets a unique endpoint URL with a secure token.
  3. Configure External Service — Paste the URL into Stripe, GitHub, etc. as their webhook destination.
  4. Inspect Requests — View all captured requests with headers, body, and metadata in real-time.

02 — Receiver Configuration

Custom Response

Configure the HTTP status code and response body returned to the calling service. Default is 200 with {"status": "ok"}.

Forward URL

Optionally relay captured webhooks to another URL after logging. Useful for debugging webhooks in development while still forwarding to your app.

03 — Testing Your Receiver

Send a test webhookbash
curl -X POST https://moqapi.dev/api/webhook-receivers/receive/abc123def456 \
  -H "Content-Type: application/json" \
  -H "X-Webhook-Secret: my-secret" \
  -d '{
    "event": "payment.completed",
    "data": {
      "id": "pay_123",
      "amount": 2999,
      "currency": "usd"
    }
  }'

The request will be logged and the configured response returned. All HTTP methods (GET, POST, PUT, PATCH, DELETE) are accepted.

04 — Log Inspection

Each captured request logs:

  • • HTTP Method — GET, POST, PUT, etc.
  • • Request Headers — All headers (host/connection filtered)
  • • Request Body — Full payload (JSON, XML, form data, etc.)
  • • Query Parameters — URL query string
  • • Source IP — Originating IP address
  • • Timestamp — When the request was received
  • • Forward Status — If forwarding enabled, the downstream response status

05 — Active / Inactive Status

Receivers can be toggled between Active and Inactive states. Inactive receivers return 410 Gone and do not log requests, which is useful for temporarily pausing webhook capture.

// Features

  • ✅ Unique secure endpoint per receiver
  • ✅ Accepts all HTTP methods
  • ✅ Full request logging (headers, body, query, IP)
  • ✅ Configurable response status and body
  • ✅ Optional request forwarding with timeout
  • ✅ Active/Inactive toggle
  • ✅ Project association for organized logging
  • ✅ CORS enabled for browser testing