Addi Authentication
Addi's merchant credit/checkout API authenticates through Auth0 (Identity as a Service) using the OAuth2 client-credentials flow. Merchants receive a client_id ("Identificador del cliente") and client_secret ("Identificador secreto del cliente") — visible in the first-party VTEX/Magento/PrestaShop plugin configuration — and exchange them at the Auth0 token endpoint for a bearer access token that is presented on subsequent API calls. A separate sandbox ("Ambiente de Desarrollo") environment is used before switching to production.
Addi secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).
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/addi-authentication"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.