Page type:
Reference. Use this page with Unified API Reference.Choose the Right Authentication Mode
| Method | Header | Best for |
|---|---|---|
| Bearer token (JWT) | Authorization: Bearer <token> | Authenticated user requests and CC-managed sessions |
| Channel API key | x-channel-access-token: <token> | Server-to-server brand or merchant workflows |
| Partner API key | x-partner-access-token: <token> | Server-to-server partner-facing or integration workflows |
Authentication Methods
Bearer Token (JWT)
Use Bearer authentication for authenticated user requests. Include the JWT token in theAuthorization header:
- Authenticated user requests
- Requests from the CreatorCommerce dashboard
- User-initiated API calls
API Key Authentication
Use API keys for server-to-server communication via the custom headers below:- Server-to-server integrations
- Backend automation
- Channel-specific operations
Getting Your Credentials
JWT Tokens
JWT tokens are obtained through the CreatorCommerce authentication flow. These tokens are typically short-lived and should be refreshed as needed.API Keys
API keys are provided when you:- Set up a channel integration
- Register as a partner
Security Rules
- Never commit credentials to version control.
- Keep API keys server-side only.
- Use HTTPS for all requests.
- Rotate keys on a regular schedule.
- Request the minimum access needed for the workflow.
- Monitor JWT expiration and implement refresh behavior where required.
Example Requests
Using Bearer Token
Using API Key
Error Responses
If authentication fails, you’ll receive a401 Unauthorized or 403 Forbidden response: