Bitfinder · OAuth Scopes

Bitfinder OAuth Scopes

OAuth 2.0 derived

Bitfinder 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://oauth2.awair.is/v2/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.

CompanyAir QualityInternet of ThingsIoTEnvironmental MonitoringSmart HomeSensorsHealthDeveloper API
Scopes: 0 Flows: authorizationCode Method: derived

OAuth endpoints

Authorization URL
https://oauth2.awair.is/v2/authorize
Token URL
https://oauth2.awair.is/v2/token
Flows
authorizationCode

Scopes (0)

Bitfinder 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-18'
method: derived
source: openapi/bitfinder-awair-openapi.yml
schemes:
- name: oauth2
  source: openapi/bitfinder-awair-openapi.yml
  flows:
  - flow: authorizationCode
    authorizationUrl: https://oauth2.awair.is/v2/authorize
    tokenUrl: https://oauth2.awair.is/v2/token
  description: OAuth 2.0 authorization-code flow for third-party access to Awair user data.
scopes: []