- API key handling
- webhook signature verification
- receiver duplicate-delivery protection
- delivery logs and replay behavior
- checks for missed events through the event feed
What sandbox gives you
Sandbox lets you:- create sandbox API keys
- review webhook endpoints for your test receiver
- create or review market-event subscription rules
- send managed test events to a selected endpoint
- inspect and redeliver managed delivery attempts
data.sandbox = truedata.generated_by = "rangler_portal"
Validate webhook delivery
- create or review a webhook endpoint that points at your test receiver
- use Send test event for that endpoint
- select
filing.neworfund.disclosure.updated - inspect the queued delivery attempt in the portal
- headers and signature
- request body shape
- source metadata
- failure category and latency
- replay and redelivery behavior
Check event-feed recovery separately
When checking for missed events:- create a sandbox API key
- read
/v1/eventsor an issuer/fund-scoped feed
Which synthetic events are supported today
Rangler currently supports sandbox generation for:filing.newfund.disclosure.updated
Recommended workflow
Use sandbox in this order:- Send a managed test event to confirm transport and signature verification
- Inspect delivery history and redeliver failures after fixing the receiver
- Read event feeds to validate earlier-record loading and missed-event handling separately
Important boundaries
- Sandbox and live should use separate API keys and distinct receiver URLs or endpoint configs in your own systems
- Treat sandbox events as integration fixtures, not market truth
- Keep a scheduled event-feed check after you enable webhooks in production