Rate limits
This page describes how much usage data you can send to the Event API and what happens when you exceed the limit. Read it before you size your ingestion pipeline or plan a backfill.
Default limit
The limit counts events, not requests. You can send single-event requests up to the limit. You do not need to batch events. You can also send batches through POST /v1/events/ingest-list. Each event in a batch counts towards the limit.
By default, a batch request can contain a maximum of 50 events. The API rejects larger batches. Split them into several requests.
Test and live are separate environments with separate limits. A load test in the test environment does not use your live capacity. But at 1,000 events per second, it cannot reproduce live throughput.
If you need more than 10,000 events per second sustained in live, or you plan a large backfill, contact Solvimon support. Give your expected peak and sustained volumes. Solvimon raises limits per platform.
Exceeding the limit
When you send events faster than your limit, the API returns 429 Too Many Requests. The Retry-After header gives the number of seconds to wait. Solvimon does not store events from a rejected request.
You can safely send a throttled request again without changes. Event idempotency uses the event reference, so Solvimon never counts an event twice. See Idempotency.
Recommended client behavior
- Store each event locally before you send it, and only mark it as delivered after a
201 Created. - On a
429, wait for the number of seconds inRetry-After, then resend. Without the header, back off exponentially starting at one second. - Spread traffic over time where you can. Sustained throughput below the limit is more reliable than short bursts at the limit.
- Log the
X-REQUEST-IDresponse header on errors so Solvimon support can trace a request.
Example
The recommended pattern is one event per request:
See Event ingestion API for the full event format and best practices.