Ingest API Rate Limits
Understand rate-limit behavior for the Ours Privacy Ingest API and plan single-event, batch, and sustained high-volume event delivery.
Ours Privacy applies protective rate limits to the Ingest API to keep event delivery reliable. We do not publish a fixed numeric request limit.
Endpoint Selection
POST /track is for ordinary real-time server-side events. POST /batch is for replay, backfill, or high-volume sends where combining events into fewer requests is appropriate.
Batching reduces network round trips. It does not exempt requests from protective rate limits.
Plan High-Volume Ingestion
For sustained high-volume ingestion or repeated request rejections, contact your account representative. They can review the integration pattern and whether single-event or batch delivery is appropriate before rollout.
The Batch Events reference documents accepted, validation, and transient batch outcomes.
Next Steps
- Quickstart: send your first event.
- Batch Events: send replay and backfill events in batches.
- Track Events: review the single-event request and response schema.
How is this guide?