Dispense API
Dispense (now AIQ Ecommerce, acquired by Alpine IQ in 2024) is B2B ecommerce and dispensary management software built specifically for cannabis retailers. This page is an independent design exercise that asks what a well-designed Dispense API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed Dispense API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing Dispense product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
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
An API for a platform like this would naturally organize around its core 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
What a Dispense API Could Look Like
If Dispense exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like Dispense: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate to a Dispense / AIQ Ecommerce storefront using API key or agency-issued credentials and obtain a session token for downstream calls.
Catalog
/productsWould list products and variants with pricing, categories, and availability filtered by store location.
Catalog
/menusWould retrieve published online menus, including category structure, deals, and per-store menu configuration.
Orders
/ordersWould pull orders with line items, fulfillment type (pickup, delivery, in-store), and status filters.
Orders
/update_order_statusWould update an order's fulfillment status as it moves through pickup, delivery, or in-store workflows.
Customers
/customersWould retrieve customer profiles, carts, and loyalty membership records for the storefront.
Inventory
/inventoryWould list stock levels and inventory records by product and store location.
Deliveries
/deliveriesWould pull 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
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require API key and authenticated sessions (including agency-issued keys) with managed session handling
Connectivity
Would build on 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
Would need 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
Design target: sub-second reads on cached catalog and order entities; multi-second writes when posting status updates
Throughput
Design target: horizontally scaled workers sized to multi-location order and menu volume
Reliability
Retry, backoff, and idempotency keys for order status and fulfillment transactions
Versioning
Clear versioning and change management would matter as Dispense evolves
Frequently asked questions
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.
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.
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual Dispense product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.