Webhooks and Event Feeds
Choose the Atlas integration mode that matches your team's engineering shape and workflow needs.
Atlas 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 Atlas can deliver matching events as soon as they are ready.
Use event feeds for backfill
Use event-feed reads for initial loading, scheduled reconciliation, missed-delivery checks, 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
Start with webhooks
Register a receiver, verify signatures, and subscribe to the events your product needs.
Use feeds to backfill
Read event feeds when you need historical context, replay windows, or a reconciliation sweep.
Keep reads as reconciliation
Event-feed reads remain the cleanest way to check for missed deliveries and replay gaps.
Trade-offs
| Concern | Event feeds | Webhooks |
|---|---|---|
| Setup effort | Lower | Higher |
| Public endpoint required | No | Yes |
| Delivery latency | Caller controlled | Lower |
| Replay and backfill | Natural | Usually paired with event feeds |
| Operational burden | Lower | Higher |
| Best fit | Backfills, reconciliation, internal jobs | Push-driven product workflows |
Recommendation
Start with webhooks for product workflows. Use event feeds for backfill and reconciliation.
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.