Use a REST API key when your server needs a custom AffiliateBase integration. Use a scoped AI connector token when connecting an MCP client such as ChatGPT, Claude, Cursor, or Codex.
Choose the credential for your workflow
| Your goal | Start here |
|---|---|
| Read or manage program records from your own application | REST API authentication |
| Connect an AI client for setup guidance or program reporting | AI Connectors and MCP |
| Install browser referral tracking | Install the tracking script |
| Receive affiliate events at your server | Set up outbound webhooks |
Keep credentials private
REST API keys belong on your server. Do not put API keys in browser scripts, public repositories, affiliate links, or screenshots. API secrets are returned once at creation, so store them securely.
Browser tracking uses your account ID and generated referral state. It does not require embedding a privileged REST API key in your website.
Give your developer the reference
The authentication reference covers supported headers and account scoping. The endpoint reference describes available resources, and the OpenAPI specification provides a machine-readable contract.
Start with one read request for the intended account before adding write operations. If authentication fails, check the key, account scope, and the exact error returned by the API.