Overview

All public routes are detailed on this page.
Our API is under development and breaking changes may happen on public endpoints. In that case a new API version will be deployed.
Our API returns JSON-encoded response and uses standard HTTP response codes.
Affilae API is available for Advertisers and Publishers.

Authentication

You must send a Token in the Authorization Header when making requests.
Your Token is available from the API Tokens menu. Your Token is a sensitive credentials.
curl --header 'Authorization: Bearer {YOUR_TOKEN}' https://rest.affilae.com/

Notes

• API endpoint: https://rest.affilae.com
• API IDs are represented as a 24 character hex string e.g. 5e2f79800000000000000000.
• API IDs (e.g. program ID / profile ID / user ID) can be retrieved from `*.me` (e.g. https://rest.affilae.com/advertiser/advertisers.me or https://rest.affilae.com/publisher/publishers.me) or `*.list` routes
• All monetary amounts are sent/returned in cents, i.e. 100 equals to 1.00.
• Datetime values sent must be in UTC (YYYY-MM-DDTHH:mm:ss.sssZ) and are returned in UTC.
• No Sandbox is provided yet.
• Endpoints are subject to rate limit (100 req/s) and may return a 429 status code (Too Many Requests).

Rate Limit Headers

Header	Description
x-ae-ratelimit-route-second-limit	Maximum number of requests per duration (e.g. 100)
x-ae-ratelimit-route-second-reset	Duration in seconds (e.g. 1)
x-ae-ratelimit-route-second-remaining	Number of requests remaining for the current duration (e.g. 42)
x-ae-ratelimit-route-second-consumed	Number of requests already used for the current duration (e.g. 58)
x-ae-ratelimit-route-second-retry-after	Number of seconds to wait before retrying after a rate-limiter failure (e.g. 0)