Churnkey · Rate Limits

Churnkey Rate Limits

Churnkey does not publish fixed numeric rate limits for its REST APIs. The documented constraints are payload-shaped rather than per-minute request caps: the Data API returns at most 10,000 sessions per request (default 100) and is paginated via limit/skip, and the bulk event endpoint accepts at most 100 events per request. GDPR deletion requests may be rejected when the data volume exceeds allowed limits. Clients should paginate large session pulls and batch event writes, and implement retry with backoff on error responses.

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

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

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

Tagged areas include Churn Prevention, Retention, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Churn PreventionRetentionRate LimitingQuotas

Limits

Sessions Per Request request
sessions
10000 max (default 100)
The Data API /sessions endpoint returns up to 10,000 sessions per call; paginate with limit and skip.
Bulk Events Per Request request
events
100
The /api/events/bulk endpoint accepts up to 100 events in one request.
REST Request Rate account
requests
not published
No fixed numeric per-minute request-rate limit is documented for the REST APIs.
DSR Deletion Volume request
records
bounded
GDPR delete requests may be rejected when the stored data volume exceeds allowed limits.

Policies

Pagination
Pull large session sets in pages using limit and skip rather than a single oversized request.
Batching
Write events in batches of up to 100 via the bulk endpoint to reduce request volume.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on any 429 responses.

Sources