JUUL · OAuth Scopes
JUUL OAuth Scopes
OAuth 2.0
probed
JUUL 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.
CompanyConsumer ProductsNicotineVapingHardwareConsumer ElectronicsBluetooth Low EnergyOpen-SourceKotlin MultiplatformRegulated Industry
Scopes: 0
Flows:
Method: probed
Scopes (0)
JUUL 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.
These are the scopes JUUL's own authorization server advertises in scopes_supported. JUUL publishes no scope reference page and no developer documentation, so no description, grant, or consent copy exists to attach — the names below are recorded verbatim and nothing is inferred about what they authorize beyond what the names themselves say. This is a first-party sign-in surface, not a developer-facing scope catalog.
These are the scopes JUUL's own authorization server advertises in scopes_supported. JUUL publishes no scope reference page and no developer documentation, so no description, grant, or consent copy exists to attach — the names below are recorded verbatim and nothing is inferred about what they authorize beyond what the names themselves say. This is a first-party sign-in surface, not a developer-facing scope catalog.
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.