APILayer · OAuth Scopes
APILayer OAuth Scopes
OAuth 2.0
probed
APILayer uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.
This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.
API MarketplaceAPI CatalogAPI DiscoveryDeveloper ToolsSaaS APIsGeolocationCurrencyData API
Scopes: 0
Flows:
Method: probed
Scopes (0)
APILayer implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.
APILayer publishes no scopes reference page. This list is read verbatim from the OAuth authorization server metadata and the MCP protected-resource descriptor, which are the only places APILayer states its scopes. Scopes apply ONLY to the hosted MCP server; the REST product APIs use an unscoped account-wide access_key.
APILayer publishes no scopes reference page. This list is read verbatim from the OAuth authorization server metadata and the MCP protected-resource descriptor, which are the only places APILayer states its scopes. Scopes apply ONLY to the hosted MCP server; the REST product APIs use an unscoped account-wide access_key.
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.