IPstack · OAuth Scopes
IPstack OAuth Scopes
OAuth 2.0
probed
IPstack 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.
GeocodingIP GeolocationLocationThreat IntelligenceNetworkingMCPPublic APIs
Scopes: 0
Flows:
Method: probed
Scopes (0)
IPstack 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 human-readable scopes/permissions reference page; the scope list exists only in the machine-readable discovery documents. That is recorded as an honest gap rather than filled in.
APILayer publishes no human-readable scopes/permissions reference page; the scope list exists only in the machine-readable discovery documents. That is recorded as an honest gap rather than filled in.
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.