Tiptop Authentication
Tiptop authenticates with API keys. Each partner account gets four keys — a public and private key pair for both the test (sandbox) and live environments. Public keys identify the account client-side (tiptop.js, mobile) and are used to generate tokens; private (server) keys are sent on server-to-server Order Management API calls in the api-key request header. Objects created in one mode cannot be manipulated by the other.
Tiptop secures its APIs with apiKey across 2 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/tiptop-authentication"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.