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, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring sessions, events, requests, and records.
An exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
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.
generated, dated 2026-07-10.
Limits
Policies
Sources
- https://docs.churnkey.co/data-api
- https://docs.churnkey.co/data-integrations/event-tracking/
- https://docs.churnkey.co/failed-payment-recovery/billing-contact-api/
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.