Webhook Quickstart: Receive SEC Filing Notifications in Your Dev Environment

Set up a free webhook endpoint in under 5 minutes and start receiving CMD+RVL outcome transitions in your local environment.

Why webhooks?

CMD+RVL outcomes carry full AI provenance — every number traced to its source filing, timestamp, and methodology. Webhooks are how that provenance flows into your systems in real time.

When you evaluate a CMD+RVL Outcome, you choose how transitions are delivered: email, Slack, or webhook.

Webhooks are the best choice for developers because:

• Structured data — JSON payloads you can parse immediately
• Real-time — transitions arrive as soon as they're detected
• Agent-ready — integrate directly with your systems, pipelines, or AI agents
• Provenance included — every delivery includes an Evidence Pack link with full audit trail

This guide shows you how to set up a free webhook endpoint for evaluation, inspect the payloads, and forward them to your local dev environment.

---

Option 1: webhook.site (Fastest)

webhook.site gives you a unique URL instantly—no signup required.

Steps

1. Go to webhook.site

   You'll immediately see a unique URL like:

   https://webhook.site/abc12345-6789-def0-1234-567890abcdef

2. Copy your webhook URL

3. Use it in your Outcome evaluation

   When discussing an outcome in discovery, ask for Webhook delivery and paste your webhook.site URL.

4. Watch transitions arrive

   When state changes occur, you'll see the POST requests appear in real-time on webhook.site with full payload inspection.

Pros & Cons

✅ Instant setup, no account needed
✅ Full request inspection (headers, body, timing)
✅ 500 requests free
⚠️ URLs expire after a few days
⚠️ No forwarding to localhost (use Option 2 for that)

---

Option 2: ngrok (Forward to localhost)

If you want transitions delivered directly to code running on your machine, use ngrok.

Steps

1. Install ngrok

   # macOS
   brew install ngrok
   
   # or download from https://ngrok.com/download

2. Sign up for a free account

   Go to ngrok.com and create a free account. Copy your auth token from the dashboard.

3. Authenticate

   ngrok config add-authtoken YOUR_AUTH_TOKEN

4. Create a webhook receiver

   Use Claude to generate a webhook receiver in your preferred language:

   📋 Copy Claude PromptPaste this into Claude to generate a webhook receiver in your preferred language.

5. Expose your local server

   ngrok http 5000

   ngrok will display a public URL like:

   Forwarding  https://a1b2c3d4.ngrok.io -> http://localhost:5000

6. Use the ngrok URL in your evaluation

   When authorizing an outcome, select Webhook and enter your ngrok URL with the

   /webhook

   path.

Now every transition will POST directly to your local server.

Pros & Cons

✅ Direct localhost delivery
✅ Real development/testing workflow
✅ Persistent URLs (with paid plan)
⚠️ Requires account signup
⚠️ Free tier has session limits

---

Option 3: RequestBin (Pipedream)

RequestBin by Pipedream offers free webhook endpoints with workflow automation.

Steps

1. Go to pipedream.com/requestbin
2. Click "Create a RequestBin"
3. Copy the generated URL
4. Use it as your webhook destination

Bonus: Forward to localhost

Pipedream can forward requests to your local machine using their CLI:

# Install Pipedream CLI
npm install -g @pipedream/cli

# Forward to localhost
pd forward --port 5000

---

Handling webhooks in production

For evaluation, the options above work great. For production, you'll want:

1. Idempotency — Use

   transition_id

   to deduplicate (we may retry on failure)
2. Signature verification — We sign payloads so you can verify authenticity
3. Acknowledgment — Return

   2xx

   quickly; process async if needed
4. Retry handling — We retry with exponential backoff on

   5xx

   or timeout

We'll cover production webhook setup when you move from evaluation to a formal monitoring plan.

---

Next steps

1. Book discovery → — Choose an outcome and ask for Webhook delivery
2. Inspect your first transition — Watch it arrive at your webhook endpoint
3. Parse and process — Build your integration logic
4. Review with us — After 14 days, we'll review delivery reliability and discuss production options

---

Related resources:

• Developer Hub — All developer tools and resources
• API Documentation — Full API reference
• MCP Servers — Agent-ready interfaces
• SEC Filing Monitor — Example outcome with webhook delivery