Portbase · OAuth Scopes
Portbase OAuth Scopes
OAuth 2.0
none
Portbase 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.
CompanyPort Community SystemLogisticsMaritimeShippingSupply ChainCustomsNetherlands
Scopes: 0
Flows:
Method: none
Scopes (0)
Portbase 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.
No OAuth2 scopes found in OpenAPI specifications. Authentication uses API keys.
No OAuth2 scopes found in OpenAPI specifications. Authentication uses API keys.
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.