Leafly website screenshot

Leafly

Leafly is a cannabis discovery marketplace where consumers research strains, read reviews, and browse and order from licensed dispensaries and brands. For retailers and point-of-sale (POS) providers, Leafly exposes a documented Menu Integration API that keeps a dispensary's Leafly menu in near-real-time sync with its system of record - pushing product/item data, variants, inventory, pricing, strain, and cannabinoid information - and a partner-gated Order (Reservations) API that lets a POS system receive and manage online orders placed on Leafly. The Menu Integration API is publicly documented (OpenAPI via ReDoc) across V1, V1.1, and V2; the Order API's full specification sits behind Cloudflare Access and is available to onboarded partners. Actual use requires a paid Leafly for Retailers subscription and a Leafly-issued menu integration key - there is no self-serve public signup or consumer-facing data API.

Leafly publishes 2 APIs on the APIs.io network: Menu API and Status API. Tagged areas include Cannabis, Dispensary, Menu Sync, POS Integration, and Retail.

Leafly’s developer surface includes authentication, documentation, signup flow, support, engineering blog, and 9 more developer resources.

40.1/100 developing ▬ flat Agent 23/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessPaidApproval
1 APIs
CannabisDispensaryMenu SyncPOS IntegrationRetailMarketplaceStrainsE-Commerce

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/leafly: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Leafly Order API

Order (Reservations) API that lets any cannabis POS provider integrate Leafly online orders into its own system, taking ownership of the order integration rather than relying on...

Leafly Menu API

The Menu API from Leafly — 2 operation(s) for menu.

Leafly Status API

The Status API from Leafly — 1 operation(s) for status.

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Pricing Plans 1

Published pricing tiers and plan structures.

Leafly Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Leafly Rate Limits

3 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Leafly Authentication

oauth2 · 1 scheme

SECURITY

Leafly Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Leafly Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Leafly Agentic Access

5 operations · 3 acting

5 operations · 3 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: leafly
url: https://raw.githubusercontent.com/api-evangelist/leafly/refs/heads/main/apis.yml
name: Leafly
kind: company
description: Leafly is a cannabis discovery marketplace where consumers research strains, read reviews, and browse and order
  from licensed dispensaries and brands. For retailers and point-of-sale (POS) providers, Leafly exposes a documented Menu
  Integration API that keeps a dispensary's Leafly menu in near-real-time sync with its system of record - pushing product/item
  data, variants, inventory, pricing, strain, and cannabinoid information - and a partner-gated Order (Reservations) API that
  lets a POS system receive and manage online orders placed on Leafly. The Menu Integration API is publicly documented (OpenAPI
  via ReDoc) across V1, V1.1, and V2; the Order API's full specification sits behind Cloudflare Access and is available to
  onboarded partners. Actual use requires a paid Leafly for Retailers subscription and a Leafly-issued menu integration key
  - there is no self-serve public signup or consumer-facing data API.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Paid · Requires approval
  confidence: high
  source:
  - plans
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/leafly.png
tags:
- Cannabis
- Dispensary
- Menu Sync
- POS Integration
- Retail
- Marketplace
- Strains
- E-Commerce
tags_raw:
- Cannabis
- Dispensary
- Menu Sync
- POS Integration
- Retail
- Marketplace
- Strains
- Ecommerce
created: '2026-07-03'
modified: '2026-07-03'
specificationVersion: '0.23'
apis:
- aid: leafly:leafly-order-api
  name: Leafly Order API
  tags:
  - Order
  - Reservations
  - POS Integration
  - Cannabis
  - Partner
  tags_raw:
  - Orders
  - Reservations
  - POS Integration
  - Cannabis
  - Partner
  image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
  humanURL: https://docs.leafly.io/reservations-api/order-api/
  baseURL: https://api.leafly.com/v2
  properties:
  - url: https://docs.leafly.io/reservations-api/order-api/
    type: Documentation
  - url: https://www.businesswire.com/news/home/20230926705189/en/Leafly-Announces-New-API-for-Order-Integration
    type: Announcement
  description: Order (Reservations) API that lets any cannabis POS provider integrate Leafly online orders into its own system,
    taking ownership of the order integration rather than relying on a bespoke Leafly-built connector. Launched in beta in
    2023, it requires the retailer to already run V2 of the Menu Integration API. The full API reference is published via
    ReDoc at docs.leafly.io/reservations-api/order-api/ but the machine-readable specification sits behind Cloudflare Access,
    so endpoint-level detail is only available to onboarded partners - endpoints here are documented at the capability level
    rather than modeled into a local OpenAPI, to avoid fabricating a surface. Contact partners@leafly.com for access.
- aid: leafly:leafly-menu-api
  name: Leafly Menu API
  description: The Menu API from Leafly — 2 operation(s) for menu.
  humanURL: https://docs.leafly.io/menu-integration-docs/v2.html
  baseURL: https://api.leafly.com/v2/menu_integration
  tags:
  - Menus
  tags_raw:
  - Menu
  properties:
  - type: OpenAPI
    url: openapi/leafly-menu-api-openapi.yml
  - type: Documentation
    url: https://docs.leafly.io/menu-integration-docs/v2.html
  - type: APIReference
    url: https://docs.leafly.io/menu-integration-docs/v2.html
- aid: leafly:leafly-status-api
  name: Leafly Status API
  description: The Status API from Leafly — 1 operation(s) for status.
  humanURL: https://docs.leafly.io/menu-integration-docs/v2.html
  baseURL: https://api.leafly.com/v2/menu_integration
  tags:
  - Status
  properties:
  - type: OpenAPI
    url: openapi/leafly-status-api-openapi.yml
  - type: Documentation
    url: https://docs.leafly.io/menu-integration-docs/v2.html
  - type: APIReference
    url: https://docs.leafly.io/menu-integration-docs/v2.html
common:
- type: CapabilityMap
  url: capabilities/leafly-capability-edges.yml
  name: Leafly Business Capability Map
- type: AgenticAccess
  url: agentic-access/leafly-agentic-access.yml
- type: DomainSecurity
  url: security/leafly-domain-security.yml
- type: Authentication
  url: authentication/leafly-authentication.yml
- type: OAuthScopes
  url: scopes/leafly-scopes.yml
- type: Website
  url: https://www.leafly.com
- type: Documentation
  url: https://docs.leafly.io/menu-integration-docs/v2.html
- type: LinkedIn
  url: https://www.linkedin.com/company/leafly
- type: Signup
  url: https://success.leafly.com/retail
- type: Support
  url: https://help.leafly.com/hc/en-us/categories/20959505132051-Developer-FAQs
- type: Plans
  url: plans/leafly-plans-pricing.yml
- type: RateLimits
  url: rate-limits/leafly-rate-limits.yml
- type: FinOps
  url: finops/leafly-finops.yml
- url: https://www.leafly.com/feed
  type: Blog
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/leafly"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/leafly/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/leafly/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.