# 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.

Source: https://docs.oursprivacy.com/docs/reference/rate-limits

Ours Privacy applies protective rate limits to the Ingest API to keep event delivery reliable.

A request rejected by a rate limit returns `429 Too Many Requests` with an empty body. Back off with exponential delay and retry.

***

## 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.

***

## 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](https://docs.oursprivacy.com/docs/reference/batch) documents accepted, validation, and transient batch outcomes.

***

## Next Steps

* **[Quickstart](https://docs.oursprivacy.com/docs/reference/quickstart):** send your first event.
* **[Batch Events](https://docs.oursprivacy.com/docs/reference/batch):** send replay and backfill events in batches.
* **[Track Events](https://docs.oursprivacy.com/docs/reference/track):** review the single-event request and response schema.
