Leafly · Rate Limits

Leafly Rate Limits

Leafly does not publish fixed numeric per-minute request limits for the Menu Integration API. Instead its documentation prescribes sync-frequency profiles: the recommended profile is a full menu POST once per day plus individual or batched PUT upserts and DELETEs as items change; an alternate profile is full POST syncs several times per hour. Menu updates are processed asynchronously - effects are not instantaneous, taking up to roughly 2.5 minutes in sandbox and up to roughly 5 minutes in production, longer under load. Leafly monitors integration health (documented in GET /status) and expects successful 200-level responses with automated, well-behaved request signatures.

Leafly Rate Limits is the machine-readable rate-limit profile for Leafly on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and seconds.

The profile also includes 3 backoff/retry policies defined and response codes documented for success.

Tagged areas include Cannabis, Menu Sync, Rate Limiting, Quotas, and POS Integration.

3 Limits
CannabisMenu SyncRate LimitingQuotasPOS Integration

Limits

Full Menu Sync (POST) integration
requests
once per day (recommended) or multiple times per hour (alternate profile)
Full menu synchronization across all items.
Item Upsert / Delete (PUT / DELETE) integration
requests
as items change (individual or batched)
Submit item-level updates and removals in near-real-time as the system of record changes.
Processing Latency integration
seconds
~150 (sandbox), ~300 (production)
Menu updates are processed asynchronously; effects are not instantaneous and vary with system load.

Policies

Sync Frequency Profiles
Use daily full POST plus batched PUT/DELETE (recommended), or full POST several times per hour (alternate).
Automated, Well-Behaved Clients
Leafly expects request signatures indicating an automated application (not manual Postman/curl) that solicits and honors 200-level responses and corrects errors on subsequent requests.
Field Validation
Use item id fields consistently, keep variant inventory reflecting stock, and set strain and cannabinoid values to null when absent.

Sources

Work with this as data

Every rate limit 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 rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • 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 rate limit 
curl "https://apis.io/api/v1/rate-limits/leafly-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

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

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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