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 3 API contracts indexed on the APIs.io network, including Menu API, Status API, and 1 more. Tagged areas include Cannabis, Dispensary, Menu Sync, POS Integration, and Retail.

The Leafly catalog on APIs.io includes 1 Spectral governance ruleset.

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

🌐 Visit website 📡 Profile data on GitHub

34.7/100 thin ▬ flat Agent 22/100 agent aware Front door AI 1/6 silent Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumApproval

1 published contract

Cannabis Dispensary Menu Sync POS Integration Retail Marketplace Strain E-Commerce

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Product Information Management

BC-2370

POST /{menu_integration_key}/menu/items

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 34.7/100 · thin

Contract Quality 9.4 / 19

Developer Ergonomics 5.0 / 15

Access Clarity 2.8 / 15

Operational Transparency 0.8 / 10

Contract Governance 1.2 / 9

Discoverability 5.0 / 8

Regulatory Posture 3.2 / 15

Create-or-Update Ergonomics 2.2 / 10

Agent readiness — 22/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/leafly/"><img src="https://apis.io/badge/leafly/card.svg" alt="Leafly on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 18.4 — up to +16.3 composite points
Developer Ergonomics scores 33.3 — up to +13.3 composite points
Contract Quality scores 50.3 — up to +12.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/leafly/apis.yml: open an issue on github.com/api-evangelist/leafly to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Regulated Retail (cannabis track-and-trace, delivery marketplaces)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

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 2

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

Leafly Integration Menu API

OPEN COLLECTION

Leafly Integration Menu Status API

OPEN COLLECTION

Leafly API pricing

Not yet checked against Leafly's own pricing page. Compiled by API Evangelist on 2026-07-03 from success.leafly.com/retail; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Leafly for Retailers Subscription paid	—
Order API Partner Integration free	—

Plan details, limits and sources →

Rate limits

Full Menu Sync (POST): once per day (recommended) or multiple times per hour (alternate profile) requests
Item Upsert / Delete (PUT / DELETE): as items change (individual or batched) requests
Processing Latency: ~150 (sandbox), ~300 (production) seconds

Compiled by API Evangelist, not yet checked against Leafly's documentation. Rate-limit details →

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

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Leafly

SLA

FinOps 1

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

Leafly Finops

FINOPS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Leafly API Rules

50 rules · 48 errors 1 warnings 1 info

SPECTRAL

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

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Signup

Signup

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

OAuthScopes

OAuthScopes

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 3

The organization behind the API

Website

Website

LinkedIn

Blog

Blog

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

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: freemium
  onboarding: approval
  trial: false
  try_now: false
  public: false
  label: Freemium · Requires approval
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/leafly.png
tags:
- Cannabis
- Dispensary
- Menu Sync
- POS Integration
- Retail
- Marketplace
- Strain
- 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
  - Partners
  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

Leafly API — frequently asked questions

Does Leafly have an API?

Yes. APIs.io lists 3 APIs from Leafly, including Leafly Order API, Leafly Menu API and Leafly Status API.

Is there an OpenAPI specification for the Leafly API?

Yes. APIs.io indexes 2 OpenAPI specifications for Leafly, each linked for download from this page.

How do I authenticate with the Leafly API?

Leafly documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Leafly Authentication.

How much does the Leafly API cost?

APIs.io lists 2 pricing plans for Leafly, with each plan's price, limits and inclusions under Pricing on this page.

Is the Leafly API ready for AI agents?

Leafly has a Kin Score of 34.7 out of 100 (thin) and an Agent Readiness score of 22.4 (agent-aware), scored by API Evangelist on 2026-11-06.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

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