specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Churnkey
providerId: churnkey
created: '2026-07-10'
modified: '2026-07-10'
reconciled: false
tags:
- Churn Prevention
- Retention
- Rate Limiting
- Quotas
description: >-
  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.
notes: >-
  No per-account or per-endpoint numeric request-rate limit is documented as of
  the review date. The values below reflect documented payload limits, not a
  published throttle. Confirm any account-level quotas with Churnkey during
  reconciliation.
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/
responseCodes:
  throttled: 429
limits:
- name: Sessions Per Request
  scope: request
  metric: sessions
  limit: 10000 max (default 100)
  notes: The Data API /sessions endpoint returns up to 10,000 sessions per call; paginate with limit and skip.
- name: Bulk Events Per Request
  scope: request
  metric: events
  limit: 100
  notes: The /api/events/bulk endpoint accepts up to 100 events in one request.
- name: REST Request Rate
  scope: account
  metric: requests
  limit: not published
  notes: No fixed numeric per-minute request-rate limit is documented for the REST APIs.
- name: DSR Deletion Volume
  scope: request
  metric: records
  limit: bounded
  notes: GDPR delete requests may be rejected when the stored data volume exceeds allowed limits.
policies:
- name: Pagination
  description: Pull large session sets in pages using limit and skip rather than a single oversized request.
- name: Batching
  description: Write events in batches of up to 100 via the bulk endpoint to reduce request volume.
- name: Backoff Strategy
  description: Implement exponential backoff with jitter and honor Retry-After on any 429 responses.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com