Choose the right retrieval pattern for the job.
Use webhooks when you need low-latency event handling. Use call-log exports when analysts need wide time windows. Use direct API pulls for near-real-time dashboards that can tolerate polling.Webhooks
Best for event-driven automation and near-real-time workflows.
Direct API
Best for dashboards and controlled reconciliation jobs.
Exports
Best for warehouse loads, finance review, and historical QA batches.
Decision matrix
| Need | Recommended pattern | Notes |
|---|---|---|
| Real-time trigger | Webhooks | Build idempotent consumers with replay tolerance |
| Hourly dashboard refresh | Direct API | Use cursor/page semantics correctly and checkpoint progress |
| Historical backfill | Export jobs | Prefer async exports for wide date windows |
Reliable data pipeline workflow
- Capture real-time outcomes via webhooks.
- Run scheduled API reconciliation for missed events.
- Schedule weekly/monthly exports for audit and finance.
- Deduplicate in warehouse by stable session/contact identifiers.
For large datasets, mixing webhook ingestion and export reconciliation gives better correctness than either pattern alone.