Dutchie API
Dutchie is North America's leading cannabis commerce platform, powering POS, ecommerce, payments, and loyalty for thousands of dispensaries. An unofficial API lets you programmatically pull retailers, menus, products, inventory, customers, orders, and transactions—and push updates like carts, checkout, and loyalty actions back into Dutchie across POS and Dutchie Plus.
What is Dutchie?
Dutchie is North America's leading cannabis commerce platform, powering over 6,500 retail and brand partners across 40+ markets and facilitating tens of billions of dollars in annual cannabis sales. Dispensaries run Dutchie as a complete operating system: in-store checkout and compliance through its point of sale, online ordering and menus through ecommerce, integrated card and pay-by-bank payments, customer retention through loyalty and marketing, and business intelligence through the Dutchie Nexus command center.
Core product areas include:
- Dutchie POS (compliant cannabis point of sale with traceability, reporting, and integrated payments)
- Ecommerce / E-Commerce Pro (omni-channel online ordering, SEO tooling, and AI-personalized menus)
- Dutchie Plus (GraphQL APIs for building fully custom dispensary ecommerce menus and checkout)
- Payments (card processing, pay-by-bank ACH, and gift card redemption)
- Loyalty & Marketing Pro (rewards programs, AI email campaigns, and mobile engagement)
- Dutchie Nexus (AI-powered command center for cross-channel reporting and operational insights)
Common data entities:
- Retailers, Locations, Menus, Categories, Brands
- Products, Variants, Pricing, Specials, Inventory
- Customers, Loyalty Accounts, Rewards, Marketing Segments
- Carts, Checkout Sessions, Orders, Transactions, Payments
- Compliance Records, Traceability Events, Reports
The Dutchie Integration Challenge
Dispensaries run mission-critical retail, menu, and payment workloads on Dutchie daily, but turning those into reliable API-driven automation is non-trivial:
- Split API surfaces: the POS API (api.pos.dutchie.com) and the Dutchie Plus GraphQL ecommerce API are separate systems with different auth, schemas, and IDs
- Partner-gated access: API keys are issued on request and the Certified Partner / Plus program gates deeper capabilities behind approval
- Rate limits and incremental sync: the POS API enforces rate limiting and pagination, requiring careful incremental-sync and idempotency handling for high transaction volumes
- Per-retailer variability: menus, taxes, specials, and compliance rules differ by location and state—generic integrations break across dispensaries
- Checkout and cart complexity: Dutchie Plus carts, checkout sessions, and order placement involve stateful GraphQL mutations that must respect compliance and inventory constraints
- Versioned schema drift: the dated GraphQL schema and evolving POS endpoints shift over time, breaking brittle hard-coded integrations
How Supergood Creates Dutchie APIs
Supergood reverse-engineers authenticated Dutchie flows, the POS API, and the Dutchie Plus GraphQL layer to deliver a single resilient API surface for your dispensary—across point of sale, ecommerce menus, and checkout.
- Handles API key issuance, partner-program access, and session continuity securely
- Manages rate limits, pagination, and incremental sync so high-volume retailers stay within Dutchie's limits
- Normalizes responses across the POS REST API and Dutchie Plus GraphQL so you integrate once and rely on consistent retailer, product, and order objects
- Aligns with per-retailer menus, taxes, specials, and state compliance rules to ensure correct, compliant access
Use Dutchie with AI agents: Dutchie MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your Dutchie products, locations, and authentication model.
- Supergood Generates and Validates Your API
We deliver a hardened Dutchie adapter tailored to your POS and Dutchie Plus configuration.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Dutchie evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Dutchie account using API key credentials and obtain a session token for downstream POS and Dutchie Plus calls.
Retailers
/retailersList retailers and locations connected to your Dutchie account with menu, tax, and compliance configuration.
Catalog
/productsRetrieve menu products, variants, pricing, specials, and live inventory across a retailer's locations.
Customers
/customersPull customer profiles, loyalty accounts, rewards balances, and marketing segments.
Orders
/create_orderBuild a cart, run a Dutchie Plus checkout session, and place an order against a retailer's menu with compliance and inventory checks.
Transactions
/transactionsRetrieve POS transactions, payments, and refunds with incremental-sync filters for status and date range.
Use Cases
Sync menus and inventory across dispensary locations
- Pull products, variants, pricing, and specials from each retailer's Dutchie menu into a single catalog - Keep live inventory in sync across POS and ecommerce channels - Surface category and brand pages for downstream marketplaces and storefronts
Automate online ordering and checkout with Dutchie Plus
- Build carts and run checkout sessions through the Dutchie Plus GraphQL layer - Place compliant orders that respect inventory, taxes, and state rules - Push order status back to custom storefronts and delivery apps
Unify POS transactions and reporting
- Stream POS transactions, payments, and refunds into BI, accounting, and reconciliation tools - Use incremental sync and idempotency to handle high daily transaction volume - Reconcile sales and compliance reports across locations
Power loyalty and marketing automation
- Sync customer profiles, loyalty accounts, and rewards balances to CRM and email tools - Trigger marketing campaigns and segments from purchase behavior - Apply and redeem rewards at checkout without manual entry
Technical Specifications
Authentication
API key credentials (issued on request) and partner-program access handled in a managed session
Connectivity
Dutchie POS REST API (api.pos.dutchie.com) plus the Dutchie Plus GraphQL ecommerce API, unified behind one surface
Response format
Normalized JSON across retailer, product, customer, order, and transaction objects
Rate limits
Adaptive throttling tuned to Dutchie's POS API rate limits to avoid retailer-side caps
Session management
Automatic session refresh, API key rotation, and credential vaulting
Data freshness
Near real-time pulls for menus, inventory, and transactions 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 placement, inventory changes, transaction completion, and loyalty events
Latency
Sub-second reads on cached menu and product entities; multi-second writes for checkout and order placement
Throughput
Horizontally scaled workers sized to high daily transaction volume across multi-location dispensaries
Reliability
Retry, backoff, and idempotency keys for orders, payments, and transaction syncs
Adaptation
Continuous monitoring of Dutchie POS endpoints, the dated GraphQL schema, and per-retailer configuration drift
Frequently asked questions
Yes. Supergood unifies the Dutchie POS REST API and the Dutchie Plus GraphQL ecommerce layer behind one normalized surface, so retailers, products, carts, orders, and transactions are consistent across both systems.
Dutchie issues API keys on request and gates deeper capabilities behind its Certified Partner and Plus programs. Supergood works with your existing Dutchie access and entitlements, and helps manage key issuance and rotation as part of the integration.
Supergood manages adaptive throttling, pagination, incremental sync, and idempotency keys so high-volume, multi-location dispensaries stay within Dutchie's POS API rate limits without dropping or duplicating data.
Yes. Through the Dutchie Plus GraphQL layer, Supergood builds carts, runs checkout sessions, and places compliant orders that respect inventory, taxes, and per-state cannabis rules.
Each location is profiled against its configured menu, taxes, specials, and state compliance rules. Supergood preserves retailer-specific fields and constraints rather than forcing a generic schema.