No Tymber-branded API. Storefronts ride on the BLAZE Partner API (apidocs.blaze.me), which uses dual-key auth and webhooks across eight resource families. Wiring it up is human-mediated: the retailer generates a BLAZE developer key, then Tymber customer service connects it.
Tymber scores D on the API Report Card. No Tymber-branded API. Storefronts ride on the BLAZE Partner API (apidocs.blaze.me), which uses dual-key auth and webhooks across eight resource families. Wiring it up is human-mediated: the retailer generates a BLAZE developer key, then Tymber customer service connects it.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Tymber is a SaaS native-ecommerce platform built specifically for licensed cannabis dispensaries.
Vertical SaaS for regulated cannabis retail. Tymber targets US licensed dispensaries (single-shop independents through small/mid-sized chains and multi-state operators) and a handful of Canadian provinces. A dispensary signs with Tymber, connects its POS (BLAZE, Treez, or a small number of other supported POS systems) so live inventory and pricing flow to the menu, and points its custom domain at the Tymber-hosted storefront.
Low. Tymber publicly cites ~150 retailers across 15 US states and 2 Canadian provinces, small versus Jane (thousands of menus), Dutchie (category leader), Weedmaps marketplace, and Leafly.
Company: Tymber (operating as the ecommerce/website wing of BLAZE Solutions, Inc.). Acquired: January 17, 2023 by BLAZE Cannabis Retail Software (Newport Beach, CA). Origin: Founded in Spain; team retained post-acquisition.
Tymber was founded in the late 2010s as one of the first widely available native-ecommerce platforms for cannabis dispensaries (versus the iframe-embed model used by early Dutchie and Jane menus).
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.
Yes. Supergood maintains an unofficial Tymber API and MCP server so AI agents and internal tools can read and write Tymber data. See the Tymber integration docs at supergood.ai/docs/tymber-api.