Cvent Event Cloud · Rate Limits

Cvent Event Cloud Rate Limits

Cvent enforces two independent limits per account: a daily call quota and a per-second call rate, both set by the account's usage tier. Every request counts against the daily quota — including requests that are themselves rejected with 429.

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

It captures 6 rate-limit definitions, across the Free, Standard, and Premium tiers, measuring calls_per_day and calls_per_second.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and note.

Tagged areas include Attendee Hub, Attendees, Bulk, Contacts, and Event Cloud.

6 Limits Throttle: 429 Quota: 429
Attendee HubAttendeesBulkContactsEvent CloudEvent ManagementEvent MarketingEventExhibitorsHybrid EventsMCPAuthenticationOnSiteOpenAPIOverlayRegistrationRESTSCIMSDKSessionsSpeakersSurveysVirtual EventsWebcastsWebhook

Limits

Free tier daily quota account
calls_per_day · day
1000
Free tier call rate account
calls_per_second · second
2
Standard tier daily quota account
calls_per_day · day
15000
Standard tier call rate account
calls_per_second · second
10
Premium tier daily quota account
calls_per_day · day
500000
Premium tier call rate account
calls_per_second · second
25

Policies

Daily quota exhaustion
On a daily-quota 429, stop making requests and wait until after midnight UTC. Retrying does not help and each rejected request still consumes quota.
Per-second back-off
Cvent's published recipe: wait 2 seconds plus a random 1–1000 ms, then double the wait for each retry up to a 16-second maximum. After five failed attempts, stop and log the error for review.
Rejected requests still count
"Every request, even those that return a 429 error, still counts against your quota." A naive retry loop therefore burns the remaining daily allowance faster than doing nothing.
Proactive monitoring
Cvent recommends reading the X-RateLimit-* headers on every response and setting usage alerts, rather than discovering limits by hitting them.

Sources