Trubrics · Rate Limits

Trubrics Rate Limits

The Trubrics ingestion API constrains throughput primarily through a documented batch limit of up to 100 events per publish request on both the publish_events and publish_llm_events endpoints. The SDKs queue events and flush on a configurable interval (default 10 seconds) or queue size (default 20 events) to batch writes efficiently. Account-level requests-per-minute or per-day quotas are not published and are not reconciled in this artifact.

Trubrics Rate Limits is the machine-readable rate-limit profile for Trubrics on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring events, seconds, and requests.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, LLM, Product Analytics, Event Tracking, and Rate Limiting.

4 Limits Throttle: 429
AILLMProduct AnalyticsEvent TrackingRate LimitingQuotasThrottling

Limits

Events Per Request (Batch Cap) request
events
100
Maximum of 100 events per publish_events or publish_llm_events POST.
SDK Flush Interval client
seconds
10
Default queue flush interval in the SDKs; configurable on init.
SDK Flush Queue Size client
events
20
Default queue size that triggers a flush in the SDKs; configurable on init.
Requests Per Minute (RPM) account
requests
see provider documentation
No published account-level RPM quota; not reconciled.

Policies

Batching
Send up to 100 events per request and rely on SDK queuing/flushing to batch writes.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources