The API Report CardAPI Index
LeafLink

LeafLink API

Cannabis B2B Wholesale Marketplace · leaflink.com

A documented REST API at developer.leaflink.com covers orders, products, inventory, and customers, versioned with dated headers. Keys are not self-serve: partners request them through LeafLink Support. There are no SDKs or first-class webhooks, and a legacy V2 API still runs alongside.

Last verified: July 2026Retail & Ecommerce
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceGOODDocumented REST API at api.leaflink.com with a developer hub at developer.leaflink.com; gating affects access, not existence.
AccessFAILNo self-serve signup; every API key request routes through LeafLink Support, adding lead time.
CoverageGOODEndpoints span orders, products, inventory, customers, line sheets, brands, promotions, and reporting.
AuthFAILJWT bearer tokens are issued only through Support; there is no OAuth flow or self-serve key management.
Docs & DXFAILNo SDKs, no sandbox, and webhooks are not first class; CORS is blocked so everything is server side.
StabilityPOORA legacy Marketplace V2 API still runs beside the dated-version API, leaving canonical endpoint support unclear.
Supergood: LeafLink has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

LeafLink scores F on the API Report Card. A documented REST API at developer.leaflink.com covers orders, products, inventory, and customers, versioned with dated headers. Keys are not self-serve: partners request them through LeafLink Support. There are no SDKs or first-class webhooks, and a legacy V2 API still runs alongside.

Tried to integrate with LeafLink?
SOURCES
API access is gated behind a Support Team request rather than self-serve developer signup, adding lead time for integrators developer.leaflink.com
CORS is explicitly disallowed for all endpoints, forcing all integrations through a server intermediary and complicating browser-side tooling developer.leaflink.com
Two parallel API surfaces (current dated API and legacy Marketplace V2) create confusion about which endpoints are canonical and supported long-term developer.leaflink.com
8 requests/second concurrent cap on top of the 300/min limit creates throttling on bulk catalog/inventory syncs typical of ERP integrations developer.leaflink.com
No officially distributed SDKs or client libraries; integrators must build directly against the JSON spec developer.leaflink.com
Webhook support is not documented as a first-class feature, pushing partners toward polling patterns that hit the rate limits faster developer.leaflink.com
Salesforce / ERP partner integrations are positioned as managed connectors rather than open recipes, so connector outages map back to LeafLink and the partner with unclear ownership leaflink.com
Abrupt 2025 pricing changes - operators report service fee jumps of 300% to 2,000% with little notice, prompting mass exits in Missouri and Colorado mogreenway.com
Forty Colorado brands publicly threatened to leave LeafLink over pricing changes they characterized as up to a 700% hike cultivated.news
Industry trust and reputational damage - long-time customers and former employees describe a shift from 'used to be the best' to operators actively coordinating mass platform migrations glassdoor.com
Multiple rounds of 2024-2025 layoffs and leadership changes coinciding with the Leaf Trade and Dama integrations, creating account-management and support continuity issues mjbizdaily.com
Pricing model perceived as opaque - customers report difficulty modeling expected fees under the 'capped, usage-based' tiers cannatechtoday.com
BBB and Trustpilot show low buyer-side ratings and unresolved complaints around order disputes, payment timing, and account suspensions bbb.org
Post-acquisition integration friction - Leaf Trade users report workflow regressions as MSO-grade features are merged into the LeafLink stack businessofcannabis.com