Summary and recommendation
CJ's public developer surface is a GraphQL API (developers.cj.com) scoped exclusively to affiliate program data - publishers, advertisers, links, and transactions.
There is no documented REST or GraphQL endpoint for creating, reading, updating, or deactivating platform users.
Personal access tokens are tied to individual CJ accounts and cannot be scoped or delegated to manage other users, which eliminates any service-account pattern for user automation.
API quick reference
| Has user API | No |
| SCIM available | No |
| SCIM plan required | N/A |
Authentication
Auth method: Not documented
User object / data model
User object field mapping is not yet verified for this app.
Core endpoints
Endpoint coverage is not yet verified for this app.
Rate limits, pagination, and events
Rate limits: Not documented
Rate-limit headers: No
Retry-After header: No
Rate-limit notes: Not documented
Pagination method: none
Default page size: 0
Max page size: 0
Pagination pointer: Not documented
Webhooks available: No
Webhook notes: No webhook system for user-management events is documented in official CJ developer or help center documentation.
Alternative event strategy: CJ's GraphQL API supports polling for advertiser/publisher relationship and transaction data, but not user lifecycle events.
SCIM API status
- SCIM available: No
- SCIM version: Not documented
- Plan required: N/A
- Endpoint: Not documented
Limitations:
- No SCIM provisioning support documented by CJ Affiliate.
- No IdP integrations (Okta, Entra, Google Workspace, OneLogin) are listed in official documentation.
- User accounts within the CJ platform are managed manually via the UI.
Common scenarios
No supported API scenarios exist for user lifecycle management in CJ.
The GraphQL API supports polling for advertiser/publisher relationship and transaction data, but no user-management events are exposed.
There are no webhooks for provisioning triggers, no SCIM endpoint, and no IdP connector (Okta, Entra ID, Google Workspace, or OneLogin) documented as of the policy date.
Any identity graph integration that depends on CJ emitting user state changes will find no supported ingestion path on the CJ side.
Scenario implementations are not yet verified for this app.
Why building this yourself is a trap
The core trap is assuming CJ's GraphQL API can be extended to cover user management - it cannot. The API is purpose-built for affiliate program operations, and CJ has not published any roadmap or beta endpoint for account or user provisioning.
Teams building an identity graph across their SaaS portfolio will need to treat CJ as a fully opaque system: no machine-readable user roster, no lifecycle events, and no deprovisioning hook. Manual UI access remains the only supported method, which breaks any automated offboarding pipeline that relies on API-driven confirmation of account removal.
Automate Commission Junction workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
