Paedae · OAuth Scopes

Paedae OAuth Scopes

OAuth 2.0 derived

Paedae 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.

Tokens are issued from https://manager.gimbal.com/oauth/token.

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.

CompanyProximityLocationBeaconsGeofencingMobile SDKAdvertisingMarketing
Scopes: 0 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://manager.gimbal.com/oauth/authorize
Token URL
https://manager.gimbal.com/oauth/token
Flows
authorizationCode

Scopes (0)

Paedae 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.

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-07-20'
method: derived
source: openapi/paedae-rest-openapi.yml
schemes:
- name: ProximityOAuth2
  source: openapi/paedae-rest-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://manager.gimbal.com/oauth/authorize
    tokenUrl: https://manager.gimbal.com/oauth/token
  description: Some Proximity APIs require an OAuth 2.0 access token instead of the organization
    server API key.
scopes: []