CJ Affiliate · Rate Limits

Cj Affiliate Rate Limits

CJ Affiliate governs API usage with per-token / per-account rate limits and paginated result sets rather than dollar-metered pricing. Exact numeric ceilings are not comprehensively published; historically CJ has enforced request-rate throttling on the REST APIs (returning HTTP 429 when exceeded) and returns large result sets in pages controlled by records-per-page and page-number parameters. The GraphQL Commission Detail and Product Search endpoints similarly page results (limit / offset, and a payloadComplete flag on commission responses signalling whether more records remain).

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

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

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

Tagged areas include Affiliate Marketing, Affiliate Network, Commission, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Affiliate MarketingAffiliate NetworkCommissionRate LimitingQuotas

Limits

REST Request Rate token
requests
not published (throttled with HTTP 429)
CJ throttles the legacy REST APIs per personal access token / account; exact ceiling not published.
GraphQL Request Rate token
requests
not published
Per-token throttling applies to commissions.api.cj.com and ads.api.cj.com; exact ceiling not published.
Records Per Page (REST) request
records
paginated via records-per-page / page-number
REST responses are paged; iterate page-number to retrieve the full set.
Commission Payload Completeness request
records
signalled by payloadComplete
publisherCommissions / advertiserCommissions return a payloadComplete boolean; page by posting date when false.

Policies

Pagination
Page through REST results with records-per-page and page-number; page GraphQL results with limit / offset.
Backoff Strategy
On HTTP 429 responses, retry with exponential backoff and jitter.
Posting-Date Windowing
Constrain commission queries to bounded sincePostingDate / beforePostingDate windows and iterate when payloadComplete is false.

Sources