Configure and receive CourtListener webhook events for docket updates and process the incoming JSON payload in your application
domain: www.courtlistener.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In your CourtListener account settings, register a publicly reachable HTTPS endpoint URL and select the DOCKET_ALERT event type
CourtListener will POST a signed JSON payload to your URL whenever a subscribed docket receives a new entry; the payload contains the docket ID, new entry data, and a timestamp
Verify the request is authentic by checking the CourtListener-provided HMAC signature in the request header against your webhook secret
Return HTTP 200 immediately on receipt; perform any heavy processing asynchronously to avoid timeout-related retries
Handle duplicate delivery by storing processed event IDs; CourtListener may retry delivery if your endpoint is temporarily unavailable
Known gotchas
Webhooks can also fire for SEARCH_ALERT, RECAP_FETCH_COMPLETE, DOCKET_ALERT_EXPIRATION, and PRAYER_GRANTED events; register only the event types you need to avoid noise
Your endpoint must use HTTPS; plain HTTP endpoints are not accepted for webhook registration
Webhook delivery is not guaranteed to be in strict chronological order; use the event timestamp field to reorder if sequence matters
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?