BLAZE API
BLAZE is a cannabis retail platform delivering point-of-sale, e-commerce, payments, and delivery software to licensed dispensaries across the U.S. An unofficial API lets you programmatically pull members, product and inventory catalogs, orders, transactions, and store configuration—and push updates like new members, cart submissions, and product changes back into BLAZE.
What is BLAZE?
BLAZE is a cannabis retail software platform that provides point-of-sale, e-commerce, payments, and delivery solutions to licensed dispensaries across multiple U.S. states. Dispensaries use BLAZE to ring up in-store sales, run online menus and ordering, process cashless payments, dispatch deliveries, manage inventory and members, and surface analytics across their operations.
Core product areas include:
- Retail Point of Sale (POS, Customer Facing Display, Self-Serve Kiosk)
- E-Commerce (Online Menu, Website Builder, Mobile App, AI Budtender, Scan to Shop)
- Payments (BlazePay cashless payments, Pay-by-Bank/ACH)
- Delivery & Operations (Driver App, Dispatch Hub)
- Analytics Reporting (Insights) and BLAZE Partner Network integrations
Common data entities:
- Members, Purchase Limits, Loyalty Points, Promotions
- Products, Categories, Brands, Batch Inventory
- Carts, Orders, Transactions, Payments
- Stores, Terminals, Tax Settings, Employees
- Deliveries, Drivers, Dispatch Routes
The BLAZE Integration Challenge
Dispensaries run mission-critical sales, compliance, and inventory workloads on BLAZE daily, but turning portal- and app-driven workflows into reliable API-driven automation is non-trivial:
- Dual-key access model: Every request requires both a Partner Key and a Developer (dispensary) Key, so headless automation must broker partner credentials before any data flows
- Partner network gates: API access is provisioned through the BLAZE Partner Network, often requiring a partnership or approval step before keys are issued
- Multi-surface data spread: POS, e-commerce cart, payments, loyalty, and delivery each have distinct object models, IDs, and lifecycle states
- Compliance-sensitive entities: Member purchase limits, batch tracking, and tax settings carry regulatory constraints that vary by state and store
- Endpoint coverage variability: The Partner API surfaces some entities richly (members, products, carts) while others live only in the POS, kiosk, or mobile apps
- Real-time event handling: Order, payment, and inventory changes flow through webhooks that need careful subscription and replay handling
How Supergood Creates BLAZE APIs
Supergood reverse-engineers authenticated browser flows together with the BLAZE Partner API to deliver a resilient API layer for your dispensary—across POS, e-commerce, payments, loyalty, and delivery surfaces.
- Handles Partner Key and Developer/dispensary Key provisioning and rotation securely
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across Members, Products, Carts, Orders, and Store Operations so you integrate once and rely on consistent objects
- Respects store-specific tax settings, purchase limits, and entitlements to ensure compliant access
Use BLAZE with AI agents: BLAZE MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your stores, modules, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready BLAZE adapter tailored to your store configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as BLAZE evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a BLAZE store using your Partner Key and Developer (dispensary) Key and obtain a session for downstream calls.
Members
/membersSearch and list member/customer records with purchase-limit tracking, loyalty status, and contact details.
Members
/create_memberCreate or update a member record, including ID verification fields and purchase-limit attributes.
Inventory
/productsQuery the product catalog with categories, brands, and batch-level inventory and pricing.
Orders
/submit_cartSubmit a consumer cart as an order with line items, promotions, taxes, and payment details.
Store Operations
/storeRetrieve store configuration including terminals, tax settings, employees, and operating details.
Use Cases
Sync members and loyalty across systems
- Pull member records, purchase limits, and loyalty points into a CRM or data warehouse - Create and update members from intake forms or marketing tools without portal clicks - Reconcile loyalty and promotion activity across stores for unified customer 360
Keep product and inventory data in sync
- Pull products, categories, brands, and batch inventory into menu and pricing tools - Push product changes and price updates back into BLAZE from a central catalog - Surface low-stock and batch-expiry events to replenishment workflows
Automate online ordering and payments
- Build and submit consumer carts with promotions, taxes, and payments through the API - Stream order and transaction events to fulfillment, BI, and accounting systems - Reconcile BlazePay and ACH payments against orders for accurate revenue reporting
Coordinate delivery and store operations
- Pull store configuration, terminals, and tax settings for multi-location reporting - Trigger dispatch and driver workflows when delivery orders are placed - Route order status and employee activity to operations dashboards
Technical Specifications
Authentication
Partner Key plus Developer (dispensary) Key passed in request headers, brokered in a managed session
Connectivity
Authenticated browser flows plus the BLAZE Partner API where exposed to the dispensary
Response format
Normalized JSON across Members, Products, Carts, Orders, and Store Operations objects
Rate limits
Adaptive throttling tuned to your store to avoid BLAZE-side limits
Session management
Automatic session refresh, key rotation, and credential vaulting
Data freshness
Near real-time pulls for members, inventory, and orders with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for order, payment, inventory, and member changes
Latency
Sub-second reads on cached entities; multi-second writes when submitting carts and payments
Throughput
Horizontally scaled workers sized to multi-store transaction volume
Reliability
Retry, backoff, and idempotency keys for cart submission, payments, and inventory updates
Adaptation
Continuous monitoring of BLAZE Partner API and product changes and store-specific configuration drift
Frequently asked questions
API access is provisioned through the BLAZE Partner Network with a Partner Key and a Developer (dispensary) Key. Supergood works with your existing keys and authenticated sessions, and can help broker provisioning where a partnership step is required.
Supergood normalizes data across POS, e-commerce cart, payments, loyalty, members, products/inventory, and store operations so you integrate once across the platform rather than per surface.
Yes. Consumer carts can be built and submitted as orders with promotions, taxes, and payment details, including BlazePay and ACH, and reconciled back against transactions.
Member records carry purchase-limit and verification attributes that Supergood preserves, and store-specific tax settings and batch tracking are respected to keep access compliant by state and store.
Yes. Store configuration, terminals, tax settings, and employee data are exposed per store, so multi-location operators can pull and reconcile data across all of their dispensaries.