Tymber API
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.
Frequently asked questions
Tymber scores D on Supergood's 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. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
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).
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official Tymber MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Tymber doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.