← Back to all docs

Distru API

Distru is a seed-to-sale cannabis ERP that centralizes inventory, orders, invoicing, manufacturing, procurement, and Metrc compliance for cultivators, processors, distributors, and retailers. An unofficial API lets you programmatically pull orders, invoices, products, inventory, purchase orders, and customer records—and push updates like new orders, invoices, and production runs back into Distru.

By Alex KlarfeldMay 30, 2026
Distru API

What is Distru?

Distru is a specialized cannabis enterprise resource planning (ERP) platform that centralizes wholesale operations, inventory management, order fulfillment, manufacturing, and regulatory compliance for cultivators, processors, distributors, and retailers. Operators use Distru to track live Metrc-synced inventory, manage orders and invoicing, run production and bill-of-materials workflows, handle procurement, and sync financials to QuickBooks—across regulated U.S. cannabis markets.

Core product areas include:

  • Inventory Management (live, Metrc-synced and BioTrack-synced tracking)
  • Order Management, Invoicing, and Order Fulfillment (Pick-n-Pack mobile app)
  • Warehouse Management and Procurement
  • Production Management (Bill of Materials, Assemblies, COGs, Production Planning, Label Printing)
  • CRM, DistruCommerce wholesale marketplace, and AI Order Agent
  • Reporting & Analytics, Cultivation Analytics, and COA (Certificate of Analysis) Management
  • Financial Management with QuickBooks Online integration

Common data entities:

  • Orders, Sales Orders, Line Items, Fulfillments
  • Invoices, Payments, Credits, Financial Records
  • Products, Batches, Packages, Inventory Locations
  • Purchase Orders, Vendors, Procurement Records
  • Companies, Contacts, Customers (CRM)
  • Production Runs, Bill of Materials, Assemblies, COAs
  • Metrc Packages, Tags, and Compliance Records

The Distru Integration Challenge

Cannabis operators run mission-critical workflows on Distru daily, but turning its portal- and integration-driven operations into reliable API-driven automation is non-trivial:

  • API key gating: Distru's API requires per-account credentials, and endpoint coverage varies by plan and enabled modules
  • Compliance coupling: Inventory, packages, and tags are tightly bound to Metrc and BioTrack state systems, so writes must respect regulatory state machines
  • Mobile-only surfaces: Pick-n-Pack fulfillment and Speed Harvesting data live primarily in mobile apps, not always exposed over the documented API
  • Manufacturing depth: Bill-of-materials, assemblies, and COGs span multiple linked objects that are hard to reconstruct from raw endpoints
  • Bidirectional integration drift: Treez, BLAZE, Dutchie, and LeafLink connections sync data both ways, so external automation must avoid conflicts
  • Financial reconciliation: Invoices, payments, and QuickBooks sync require careful effective-date and status handling to stay in balance

How Supergood Creates Distru APIs

Supergood reverse-engineers authenticated browser flows and Distru's published API surface to deliver a resilient, normalized API layer for your Distru account—covering inventory, orders, invoicing, procurement, and production.

  • Handles API key authentication and authenticated session flows securely
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across Orders, Invoices, Products, Inventory, and Procurement so you integrate once and rely on consistent objects
  • Respects Metrc/BioTrack compliance state and your account's enabled modules to ensure valid writes

Use Distru with AI agents: Distru MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your modules, enabled integrations, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a production-ready Distru adapter tailored to your account configuration and compliance state.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Distru evolves.

distru

API Endpoints

Authentication

POST/authenticate

Authenticate to a Distru account using an API key and obtain a session token for downstream calls.

Orders

GET/orders

List sales orders with filters for status, customer, location, and date range, including line items and fulfillment state.

Orders

POST/create_order

Create a new sales order with line items, customer, and delivery details against your Distru configuration.

Invoicing

GET/invoices

Retrieve invoices, payments, and credits with status and customer filters for financial reconciliation.

Inventory

GET/products

Pull products, batches, packages, and live Metrc-synced inventory across locations.

Procurement

GET/purchase_orders

List purchase orders and vendor records with status, vendor, and date filters for procurement workflows.

Use Cases

Sync orders and invoices into accounting and BI

- Pull orders, line items, and fulfillment status into a single warehouse - Stream invoice, payment, and credit events to QuickBooks, NetSuite, or BI tools - Reconcile customer and company records across CRM and finance systems

Automate inventory and Metrc compliance reporting

- Pull live Metrc-synced product, batch, and package inventory across locations - Surface low-stock and aging-inventory events to replenishment workflows - Push validated package and tag updates that respect state compliance rules

Streamline procurement and vendor management

- Sync purchase orders and vendor records into spend-analysis tools - Trigger receiving and put-away workflows when inbound packages arrive - Match purchase orders against invoices for three-way reconciliation

Power production and COGs analytics

- Pull production runs, bill-of-materials, and assemblies into manufacturing dashboards - Track cost of goods across batches and finished products - Attach COA results to packages and surface them to customers

Technical Specifications

Authentication

API key credentials handled in a managed session, with secure token storage

Connectivity

Distru's published REST API surface plus authenticated browser flows where endpoints are not exposed

Response format

Normalized JSON across Orders, Invoices, Products, Inventory, and Procurement objects

Rate limits

Adaptive throttling tuned to your account to avoid Distru-side and Metrc-side limits

Session management

Automatic session refresh, credential rotation, and key validation

Data freshness

Near real-time pulls for orders, invoices, and inventory 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 creation, invoice status, inventory changes, and fulfillment updates

Latency

Sub-second reads on cached entities; multi-second writes when posting orders and production runs

Throughput

Horizontally scaled workers sized to multi-location order and inventory volume

Reliability

Retry, backoff, and idempotency keys for orders, invoices, and inventory transactions

Adaptation

Continuous monitoring of Distru releases, Metrc/BioTrack changes, and account configuration drift

Frequently asked questions

Yes. Supergood normalizes data across Distru's order, invoicing, and inventory surfaces, so you can pull sales orders, line items, products, batches, and live Metrc-synced packages through a single consistent API.

Supergood works with your existing Distru account credentials, including the API key Distru issues for your account. We handle key storage, rotation, and session management so you do not have to build that plumbing yourself.

Distru inventory is tightly coupled to Metrc and BioTrack state systems. Supergood respects those compliance state machines on writes, so package, tag, and inventory updates stay valid against your state's regulatory requirements.

No. Distru's bidirectional integrations sync data both ways. Supergood coordinates with those flows and applies idempotency and change detection so external automation does not create duplicate or conflicting records.

Yes. Production runs, bill-of-materials, assemblies, and COGs are exposed through the same normalized API surface, so manufacturing data sits alongside order, invoice, and inventory entities.

Ready to get a real API?