Webhooks for Insider and Congress Filings: Push Instead of Polling

How Bourse pushes new Form 4, Congress, Trump, Cabinet and Form 144 filings to your HTTPS endpoint, how to verify the signature and how to filter by ticker.

Polling an API every few seconds wastes requests and still arrives late. With webhooks Bourse sends new filings to your server as they are processed.

Key takeaways

• Register up to 5 HTTPS endpoints in the app (Settings, API, Webhooks) on Premium, pay-as-you-go, API Pro or Enterprise.
• Choose event types: congress, insiders, trump, cabinet, form144, and optionally a list of tickers.
• Every 5 minutes Bourse POSTs a JSON batch of new events to each endpoint.
• Each request is signed: Bourse-Signature: t=<unix>,v1=<hex>, an HMAC-SHA256 of "<t>." + raw body with your webhook secret.

Payload

`` {"id": "6f1c...", "created": "2026-11-11T14:05:00Z", "count": 1, "events": [{"type": "insiders", "at": "2026-11-11T14:03:12Z", "data": {"ticker": "NVDA", "side": "buy", "value": 120500}}], "source": "Bourse (bourse.pl)"} ``

Verify in Python

`` import bourse ok = bourse.verify_webhook(secret, request.headers["Bourse-Signature"], request.get_data()) ``

Reject requests older than five minutes and compare signatures in constant time; the helper does both. Webhooks work with n8n, Zapier (Catch Hook), Make and any server. The event schema is in the API reference; setup steps are on the developer page.

Bourse provides financial data and editorial information, parts of which are generated by AI. This page is for general education only. It is not personalised investment advice or a recommendation to buy or sell any financial instrument. Make your own decisions.