TurboRater · Rate Limits

Turborater Rate Limits

TurboRater (ITC / Zywave) does not publish numeric rate limits for its rating API. Because the API is partner-gated, throughput expectations and any quota are set per partner agreement rather than through a public developer policy. ITC does publish one relevant constraint on the other side of the transaction: it requires partners to meet a minimum response time when returning real-time rates, to protect the agent experience. Effective quote volume is governed by the partner's subscription and carrier appointments, not by a documented per-minute request cap.

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

It captures 3 rate-limit definitions, measuring requests, quotes, and latency.

The profile also includes 2 backoff/retry policies defined.

Tagged areas include Insurance, Comparative Rating, Real-Time Rating, Rate Limiting, and ITC.

3 Limits
InsuranceComparative RatingReal-Time RatingRate LimitingITCZywave

Limits

Rating API Requests partner
requests
not published
No fixed numeric request-rate limit is documented; governed by the partner agreement.
Quote Volume account
quotes
per subscription
Effective quote throughput is bounded by the partner's subscription and carrier appointments.
Real-Time Response Time partner
latency
minimum required (ITC-set)
ITC requires partners to meet a minimum response time when returning real-time rates to preserve the agent experience.

Policies

Partner Provisioning
Access, quota, and carrier appointments are provisioned per partner rather than through a public self-serve policy.
Backoff Strategy
Consumers of the rating API should implement retry with exponential backoff and jitter, and honor any Retry-After guidance provided in the partner agreement.

Sources