Dispense API
Dispense (now AIQ Ecommerce, acquired by Alpine IQ) is SEO-focused cannabis ecommerce and dispensary management software powering online menus, pickup, delivery, kiosk, and drive-through ordering for cannabis retailers. An unofficial API lets you programmatically pull orders, products, menus, customers, inventory, and delivery records—and push updates like menu changes, order status, and customer records back into the dispensary's own Dispense storefront.
What is Dispense?
Dispense (now AIQ Ecommerce, acquired by Alpine IQ in 2024) is B2B ecommerce and dispensary management software built specifically for cannabis retailers. Dispensaries use it to run SEO-optimized online menus, manage pickup, delivery, in-store, kiosk, and drive-through orders, process payments, and engage customers through CRM, chat, deals, and loyalty—while retaining ownership of their own customer data rather than operating on a consumer marketplace.
Core product areas include:
- Ecommerce and SEO Menu (online ordering storefront and digital menuing)
- Order Management (pickup, delivery, in-store, kiosk, and drive-through)
- Dispensary Management and Payments
- Marketing, CRM, Customer Chat, Deals and Offers
- Analytics and Mobile App, connected to the wider Alpine IQ loyalty and data ecosystem
Common data entities:
- Products, Menus, Categories, Variants, Pricing
- Orders, Line Items, Fulfillment Type (pickup/delivery/in-store), Order Status
- Customers, Profiles, Loyalty Membership, Carts
- Inventory, Stock Levels, Store/Location records
- Deliveries, Routes, Deals and Offers
The Dispense Integration Challenge
Dispensaries run their storefront and order pipeline on Dispense every day, but getting your own commerce data out as reliable, API-driven automation is harder than it looks:
- Key-gated access: The Blueprint API is partner/key-gated—agencies must obtain keys from each retail client, and key issuance and scope vary by account
- Trapped commerce data: Your orders, customers, and menu performance live inside the hosted storefront, with limited self-serve export beyond the built-in analytics dashboard
- Post-acquisition surface drift: As Dispense merges into AIQ Ecommerce and the Alpine IQ loyalty/data stack, endpoints, auth, and resource shapes shift across the consolidation
- POS and fulfillment coupling: Menus and inventory sync from third-party cannabis POS systems, so order and stock data spans multiple integrations with their own IDs and timing
- Cannabis compliance constraints: Customer, age-verification, and purchase-limit data carry regulatory handling requirements that generic ecommerce connectors ignore
- Per-store configuration: Multi-location operators have store-specific menus, pricing, deals, and fulfillment options that break one-size-fits-all integrations
How Supergood Creates Dispense APIs
Supergood reverse-engineers authenticated browser flows and the Blueprint API surface to deliver a resilient API layer for your Dispense / AIQ Ecommerce storefront—so your own orders, menus, and customers become programmable data you control.
- Handles API-key and authenticated-session access securely, including agency-issued keys
- Maintains session continuity with automated refresh and change detection across the AIQ consolidation
- Normalizes responses across Products, Menus, Orders, Customers, Inventory, and Deliveries so you integrate once
- Aligns with per-store menus, pricing, and fulfillment options for multi-location operators
Use Dispense with AI agents: Dispense MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your stores, fulfillment types, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Dispense adapter tailored to your storefront configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Dispense evolves into AIQ Ecommerce.
API Endpoints
Authentication
/authenticateAuthenticate to a Dispense / AIQ Ecommerce storefront using API key or agency-issued credentials and obtain a session token for downstream calls.
Catalog
/productsList products and variants with pricing, categories, and availability filtered by store location.
Catalog
/menusRetrieve published online menus, including category structure, deals, and per-store menu configuration.
Orders
/ordersPull orders with line items, fulfillment type (pickup, delivery, in-store), and status filters.
Orders
/update_order_statusUpdate an order's fulfillment status as it moves through pickup, delivery, or in-store workflows.
Customers
/customersRetrieve customer profiles, carts, and loyalty membership records for the storefront.
Inventory
/inventoryList stock levels and inventory records by product and store location.
Deliveries
/deliveriesPull delivery orders, routes, and delivery status for fulfillment tracking.
Use Cases
Sync orders and menus into your warehouse
- Pull orders, line items, and fulfillment type from every store into a single data warehouse - Stream menu, product, and pricing changes to downstream BI and merchandising tools - Reconcile per-store menu configuration and deals across multi-location operations
Automate customer and loyalty workflows
- Sync customer profiles, carts, and loyalty membership into your CRM and marketing stack - Trigger win-back and abandoned-cart campaigns from order and cart events - Unify Dispense customer records with the wider Alpine IQ loyalty ecosystem
Keep inventory and fulfillment in sync
- Pull stock levels and inventory by product and location for availability monitoring - Update order status as items move through pickup, delivery, and in-store fulfillment - Surface low-stock and out-of-stock products to ops and purchasing workflows
Power delivery and route operations
- Pull delivery orders, routes, and delivery status for real-time tracking - Feed delivery events into customer notifications and ops dashboards - Reconcile delivery throughput against order volume for capacity planning
Technical Specifications
Authentication
API key and authenticated sessions (including agency-issued keys) handled in a managed session
Connectivity
Authenticated browser flows plus the Blueprint headless commerce API surface where exposed by the storefront
Response format
Normalized JSON across Products, Menus, Orders, Customers, Inventory, and Deliveries objects
Rate limits
Adaptive throttling tuned to your storefront to avoid platform-side limits during the AIQ consolidation
Session management
Automatic session refresh, key rotation, and credential handling for retailer and agency access
Data freshness
Near real-time pulls for orders and inventory with optional scheduled batch syncs for menus and customers
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for new orders, order status changes, menu updates, and inventory changes
Latency
Sub-second reads on cached catalog and order entities; multi-second writes when posting status updates
Throughput
Horizontally scaled workers sized to multi-location order and menu volume
Reliability
Retry, backoff, and idempotency keys for order status and fulfillment transactions
Adaptation
Continuous monitoring of Dispense / AIQ Ecommerce releases and post-acquisition Alpine IQ platform changes
Frequently asked questions
Yes. Dispense was acquired by Alpine IQ in 2024 and is being consolidated into AIQ Ecommerce. Supergood targets your live storefront surfaces and continuously monitors the consolidation so your integration keeps working as endpoints and auth shift.
Supergood works with your existing access. The Blueprint API is key-gated—retailers receive keys directly and agencies obtain them from their retail clients—and we operate against whatever entitlements your account already has, including authenticated browser sessions where key access is limited.
Yes. Multi-location operators get store-scoped access to menus, pricing, orders, inventory, and deliveries, with per-store configuration preserved rather than flattened into a single generic schema.
Customer, age-verification, and purchase-limit fields are preserved with their regulatory context. Supergood normalizes these alongside order and customer entities without stripping the compliance-relevant attributes generic connectors drop.
Yes. Beyond reads, the API supports pushing order status updates and menu/pricing changes back into the storefront, with idempotency and retry handling on write transactions.