Leafly · OAuth Scopes

Leafly OAuth Scopes

OAuth 2.0 derived

Leafly 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://api.leafly.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.

CannabisDispensaryMenu SyncPOS IntegrationRetailMarketplaceStrainsEcommerce
Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.leafly.com/oauth/token
Flows
clientCredentials

Scopes (0)

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

Leafly's Menu Integration API V2 uses the OAuth2 client credentials grant with no published scopes - the upstream OpenAPI (https://docs.leafly.io/menu-integration-docs/v2.json) declares an empty scopes map and access is instead tied to a Leafly-issued menu_integration_key identifying the retailer.

📄 Provider scope reference: https://docs.leafly.io/menu-integration-docs/v2.html

Source

OAuth Scopes

leafly-scopes.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/leafly-menu-integration-openapi.yml
docs: https://docs.leafly.io/menu-integration-docs/v2.html
note: Leafly's Menu Integration API V2 uses the OAuth2 client credentials grant
  with no published scopes - the upstream OpenAPI (https://docs.leafly.io/menu-integration-docs/v2.json)
  declares an empty scopes map and access is instead tied to a Leafly-issued
  menu_integration_key identifying the retailer.
schemes:
- name: OAuth2ClientCredentials
  source: openapi/leafly-menu-integration-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.leafly.com/oauth/token
scopes: []