Skip to main content
Rangler supports webhook delivery and event-feed reads.

​
Use webhooks for product workflows

Use webhooks for push delivery into products, alerting systems, and backend workflows. This is the default path for customer-facing integrations because Rangler can deliver matching events as soon as they are ready.

​
Use event feeds for earlier records

Use event feeds for initial loading, scheduled checks for missed deliveries, and teams that cannot operate a public HTTPS receiver yet. The same event data is available through GET /v1/events, GET /v1/companies/{company_id}/events, and GET /v1/funds/{fund_id}/events.

​
Many teams should use both

1

​
Start with webhooks

Register a receiver, verify signatures, and subscribe to the events your product needs.
2

​
Use feeds to load earlier events

Read event feeds when you need earlier history, a specific time range, or a check for missed deliveries.
3

​
Keep reads as a safety check

Event-feed reads remain the cleanest way to check for missed deliveries and replay gaps.

​
Trade-offs

​
Recommendation

Start with webhooks for product workflows. Use event feeds for earlier records and checks for missed deliveries. See SDKs, Events, and Webhooks for the integration surface and delivery contract. For workflow-specific examples, start with Fund Monitoring, Issuer Monitoring, and Sandbox Testing.