← Back to all docs

Canix API

Canix is a cannabis ERP and seed-to-sale platform that runs inventory, compliance, cultivation, labor costing, and order workflows for cultivators, manufacturers, and distributors. Canix offers a public API, and a normalized integration layer lets you programmatically pull inventory and packages, plants, harvests, sales and purchase orders, invoices, and Metrc compliance data—and push updates like new packages, tasks, and order records back into Canix.

By Alex KlarfeldMay 30, 2026
Canix API

What is Canix?

Canix is a cannabis ERP and seed-to-sale platform that streamlines operations for cannabis cultivators, manufacturers, and distributors across the supply chain. Operators use Canix to manage inventory, run Metrc compliance with bi-directional data sync, forecast cultivation, track labor costs and COGS, and process sales orders, purchase orders, and invoices—with an offline-enabled mobile app and RFID/Bluetooth scale integrations to accelerate harvest and packaging workflows.

Core product areas include:

  • Inventory Management (cannabis and non-cannabis inventory across the supply chain)
  • Compliance (Metrc integration with bi-directional data synchronization via Metrc Connect)
  • Cultivation Forecasting (nursery tools for cuttings, clones, and production trend analysis)
  • Labor Costing and Task Management (employee task tracking with time estimations for COGS)
  • Invoicing & Purchase Orders (sales orders, vendor relationships, and accounting sync)
  • Business Intelligence Reporting (custom charts and analytics across multiple facilities)
  • RFID Integration and Canix Mobile (Bluetooth scale support and offline-enabled mobile app)

Common data entities:

  • Inventory Items, Packages, Lots, Tags
  • Plants, Plant Batches, Harvests, Strains
  • Sales Orders, Purchase Orders, Invoices, Line Items
  • Customers, Vendors, Facilities, Locations
  • Tasks, Labor Entries, COGS Records
  • Metrc Compliance Records, Transfers, Manifests

The Canix Integration Challenge

Cannabis operators run mission-critical inventory and compliance workloads on Canix daily, but turning those workflows into reliable API-driven automation comes with real friction:

  • API key provisioning: Programmatic access runs through a "Request API Key" portal, so each integration depends on per-account keys and scoped permissions
  • Metrc compliance coupling: Inventory, packages, plants, and transfers are tightly synced with state Metrc systems, so data shape and lifecycle states vary by state and license type
  • Mobile-and-RFID-captured data: Harvest weights, scans, and task entries flow through the offline mobile app, so some data lands asynchronously and must reconcile on sync
  • Multi-facility spread: Cultivation, manufacturing, and distribution facilities each carry their own inventory, locations, and reporting scopes that must be stitched together
  • Accounting handoffs: Invoices, purchase orders, and labor costs sync to QuickBooks, Sage, and other systems, each with its own field mapping and timing
  • Endpoint coverage variability: The public Swagger catalogue covers many operations, but coverage and object shapes differ across inventory, cultivation, sales, and compliance domains

How Supergood Creates Canix APIs

Supergood combines Canix's public API with reverse-engineered authenticated flows to deliver a resilient, normalized API layer for your Canix account—across inventory, cultivation, sales, and Metrc compliance.

  • Manages API key and authenticated session handling securely, including MFA where present
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across inventory, plants, harvests, orders, and Metrc records so you integrate once against consistent objects
  • Reconciles mobile- and RFID-captured data and multi-facility scopes into a single coherent surface

Use Canix with AI agents: Canix MCP Server →

Getting Started

  • Schedule Integration Assessment

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

  • Supergood Generates and Validates Your API

We deliver a production-ready Canix adapter tailored to your account configuration and entitlements.

  • Deploy with Monitoring

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

canix

API Endpoints

Authentication

POST/authenticate

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

Inventory

GET/inventory

List inventory items and packages across facilities with filters for product type, location, tag, and status.

Inventory

POST/create_package

Create a new package or repackage existing inventory, syncing tags and quantities with Metrc compliance.

Cultivation

GET/harvests

Retrieve harvests, plant batches, and plant records with strain, weight, and lifecycle-stage filters.

Sales

GET/orders

Pull sales orders, purchase orders, and line items with customer, vendor, and status filters.

Sales

POST/create_order

Create a sales order or invoice against existing customer and inventory records.

Use Cases

Sync inventory and compliance data with Metrc

- Pull inventory items, packages, and tags across facilities into a single warehouse - Reconcile Canix records against Metrc transfers and manifests to maintain compliance - Stream package and quantity changes to downstream BI and reporting tools

Automate cultivation and harvest tracking

- Pull plants, plant batches, and harvests with strain and weight detail - Capture RFID- and scale-driven harvest weights from the mobile app without manual entry - Feed cultivation forecasts and yield trends into planning tools

Reconcile orders, invoices, and accounting

- Sync sales orders, purchase orders, and invoices into QuickBooks, Sage, or your GL - Match vendor purchase orders and line items against receivables - Surface delinquent invoices and order status to finance workflows

Track labor costs and COGS

- Pull task and labor entries with time estimations for accurate COGS - Allocate labor costs from raw materials to finished goods across facilities - Push task assignments and completion status back into Canix

Technical Specifications

Authentication

API key provisioned through Canix's Request API Key portal, plus authenticated session handling in a managed session

Connectivity

Canix's public REST API (Swagger/OpenAPI catalogue) plus reverse-engineered authenticated flows where needed

Response format

Normalized JSON across inventory, plants, harvests, orders, and Metrc compliance objects

Rate limits

Adaptive throttling tuned to your account to stay within Canix and Metrc Connect limits

Session management

Automatic session refresh, API key rotation, and MFA handling where present

Data freshness

Near real-time pulls for inventory, orders, and compliance with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for package changes, harvest events, order status, and compliance updates

Latency

Sub-second reads on cached entities; multi-second writes when posting packages and orders through compliance workflows

Throughput

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

Reliability

Retry, backoff, and idempotency keys for package creation, order posting, and Metrc sync

Adaptation

Continuous monitoring of Canix releases, Metrc Connect changes, and account-specific configuration drift

Frequently asked questions

Yes. Canix offers an open API with Swagger documentation and a Request API Key portal. Supergood builds on top of it—and fills gaps with authenticated flows—to deliver a fully normalized, resilient integration surface.

Canix's foundation is its bi-directional Metrc sync via Metrc Connect. Supergood exposes inventory, packages, plants, transfers, and manifests as normalized objects so compliance data sits alongside your inventory and order entities.

Yes. RFID- and scale-driven harvest weights, plant batches, and task entries captured in Canix Mobile are reconciled on sync and surfaced through the same API, so offline-captured data is available programmatically.

Yes. Cultivation, manufacturing, and distribution facilities are stitched into a single surface, with location, facility, and Metrc state context preserved on each record rather than forced into a generic schema.

Yes. Beyond reads, the API supports writes such as creating packages, sales orders, invoices, and task assignments, with retry and idempotency handling to keep Canix and Metrc in sync.

Ready to get a real API?