API overview and authentication

The Affilinext REST API lets you pull campaigns, clicks, conversions and reports into your own tools, and send clicks and conversions from your server.

Base URL

https://app.affilinext.com/api/v1

If your network runs Affilinext on its own domain, use that domain instead. Every endpoint is served over HTTPS and returns JSON.

Get an API key

The full key starts with ak_ and is shown only once, when it's created. Store it in a secret manager, not in source code. See Create and use API keys for more.

What a key can see

Every key is tied to an account, and the API only ever returns that account's data:

A key stops working immediately if it's revoked or if its account is deactivated.

Authenticate

Send the key in a header on every request:

Authorization: Bearer ak_your_key

x-api-key: ak_your_key works too. You can also pass ?apiKey= in the URL, but avoid it — URLs end up in proxy logs and browser history.

Your first request

Check that your key works and see which account it belongs to:

curl https://app.affilinext.com/api/v1/me \
  -H "Authorization: Bearer ak_your_key"

{
  "success": true,
  "message": "OK",
  "apiKey": { "id": "key_8f2c", "name": "Reporting sync", "role": "affiliate" },
  "advertiserId": null,
  "affiliateId": "aff_102"
}

role is affiliate for publisher keys, advertiser for advertiser keys, and admin, readonly or reports for network keys.

Response format

Every response is JSON with a success flag. Errors also carry an error message — see Errors, rate limits and retries.

List endpoints are paginated and return:

{
  "success": true,
  "total": 1284,
  "limit": 50,
  "offset": 0,
  "rows": [ ... ]
}

Dates in filters (from, to) are YYYY-MM-DD in UTC and include the whole day. Timestamps in responses are ISO 8601 in UTC.

Endpoints