Awin Affiliate Authentication
Awin authenticates with a single long-lived token bound to a USER, not to an account and not to an application. The token is created by a human in the platform UI at https://ui.awin.com/awin-api after re-entering their password, and it grants access to every publisher and advertiser account that user can reach - Awin states this explicitly: "If you have access to 10 different Awin publisher accounts via our website, then your personal API token grants you access to data from all of those 10 accounts." Awin describes this as OAuth 2.0, but only bearer-token presentation (RFC 6750) is implemented: there is no authorization endpoint, no token endpoint, no client registration, no grant flow, no refresh and no scopes.
Awin secures its APIs with http and apiKey across 3 declared security schemes, as derived from its OpenAPI definitions.
Security Schemes
Source
Authentication Profile
Work with this as data
Every security artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for security posture
4 MCP tools reach this
find_securityBrowse and filter every security artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/security/awin-affiliate-authentication"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.