Integrate menu and order data via the Weedmaps API
domain: developer.weedmaps.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Apply to Weedmaps' integrations team to become an approved Integrator; as of this writing Weedmaps is not onboarding new integration partners, though applications are kept on file.
Once approved, authenticate using OAuth 2.0 client credentials, and have the retailer (listing owner) explicitly grant your integration access before you can read or write their data.
For menu sync, call the Menu API to push item availability and pricing from your POS, linking items to Weedmaps' category, cannabinoid, terpene, and strain data.
For order handling, use the Orders API, which requires an existing live menu integration to already be in place.
Configure a callback/postback URL to receive incoming online orders in real time, then push status updates (confirmed, ready, cancelled) back through the API.
Consult the published OpenAPI spec for the Orders API for the full current endpoint and schema reference.
Known gotchas
New-partner onboarding is currently closed, which materially limits who can build this integration today regardless of technical readiness.
A merchant with multiple locations must have the POS integration enabled separately per individual listing; there is no bulk-enable across locations.
All calls require HTTPS with a valid OAuth access token; there is no unauthenticated or API-key-only access path documented.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?