Toshl Authentication
The Toshl API supports two authentication methods: OAuth 2.0 bearer tokens (authorization code and implicit grants; user-revocable) and HTTP Basic authentication using long-lived personal tokens created in the Toshl account settings (apps section, available since 26 April 2016). Access tokens default to a 3600-second lifetime with refresh tokens for renewal; refresh tokens can be revoked by users or Toshl staff at any time. Client registration (client_id and client_secret) is required before using OAuth.
Toshl secures its APIs with oauth2 and http-basic across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and implicit 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/toshl-authentication"
curl "https://apis.io/api/v1/security?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.