Conviva Rate Limits
Conviva rate limits are expressed as CONCURRENT requests per minute per c3 account, and they are a function of both request count and applied filters: "A 500 concurrent request limit is reached with either 100 requests with 5 filters or 500 requests with 1 filter." Historical Metrics V3 and Sessions V3 SHARE one 400-concurrent pool. A separate global ceiling of 3000 requests per 5 minutes applies per IP address across all endpoints. Response size is capped independently of request rate.
Conviva Rate Limits is the machine-readable rate-limit profile for Conviva on the APIs.io network, in the API Commons Rate Limits shape.
It captures 6 rate-limit definitions, measuring requests and concurrent_requests.
Limit state is signalled in the rateLimitRemaining, retryAfter, and note response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and payloadTooLarge.
Tagged areas include Rate Limiting, Analytics, and Streaming.
rateLimitRemainingretryAfternote
Limits
Sources
- https://docs.conviva.ai/connect-data/apis/
- https://docs.conviva.ai/api/apis/conviva-vsi-api/metrics-v3-api-guide/
- https://docs.conviva.ai/api/apis/conviva-vsi-api/precision-policy-api/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.