Wingtra · OAuth Scopes
Wingtra OAuth Scopes
OAuth 2.0
probed
Wingtra 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.
CompanyDronesUAVAerial SurveyingMappingPhotogrammetryGeospatialSurveyingLiDARHardwareSwitzerland
Scopes: 0
Flows:
Method: probed
Scopes (0)
Wingtra 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.
Wingtra publishes no scope or permission reference — there is no developer portal to publish one on. The scopes below are the `scopes_supported` array the Wingtra Auth0 tenant serves in its own OIDC discovery document, fetched anonymously. They are standard OIDC identity scopes: the tenant advertises no Wingtra product scope (nothing for drones, licences, sites, flights or files), which means the portal GraphQL API and the WingtraCLOUD REST API do not express authorization as OAuth scopes. Authorization is carried instead by tenant membership and by the `assigned_roles` array the login mutation returns, neither of which is documented publicly. scope_count counts what is served, not what governs the API.
Wingtra publishes no scope or permission reference — there is no developer portal to publish one on. The scopes below are the `scopes_supported` array the Wingtra Auth0 tenant serves in its own OIDC discovery document, fetched anonymously. They are standard OIDC identity scopes: the tenant advertises no Wingtra product scope (nothing for drones, licences, sites, flights or files), which means the portal GraphQL API and the WingtraCLOUD REST API do not express authorization as OAuth scopes. Authorization is carried instead by tenant membership and by the `assigned_roles` array the login mutation returns, neither of which is documented publicly. scope_count counts what is served, not what governs the API.
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.