Trym API
Trym is cannabis farm-management software for commercial cultivators, combining full Metrc compliance, plant and harvest tracking, wireless sensors, crop steering, and team workflows. An unofficial API lets you programmatically pull plants, harvests, tasks, lab results, and sensor readings—and push updates like harvest weights, Metrc actions, and task assignments back into Trym.
What is Trym?
Trym is cannabis farm-management software built specifically for commercial growers. Cultivators use Trym as a full Metrc compliance system—tracking plants through their growth cycles, recording harvest weights, and reporting to state traceability—while also managing team tasks, monitoring climate and root-zone sensors, steering crops to improve yields, and analyzing production data. Trym was acquired by Canix in January 2026.
Core product areas include:
- Metrc Compliance (nationwide integration, plant tagging, harvest reporting, package and transfer actions)
- Cultivation Management (plant tracking through growth phases, mother and clone management, batch workflows)
- Harvest & Weights (mobile tag scanning, RFID touchless harvesting, Bluetooth Ohaus scale capture)
- Sensors & Crop Steering (Aranet, Growlink, TrolMaster, Argus integrations for climate and substrate EC/WC data)
- Team Management (task workflows, assignments, and in-app communication)
- Analytics & Lab Results (production dashboards, Confident Cannabis lab-result linking, yield reporting)
Common data entities:
- Plants, Batches, Strains, Growth Phases, Metrc Tags
- Harvests, Plant Weights, Packages, Waste Records
- Tasks, Assignments, Team Members, Notes
- Sensor Readings (temperature, humidity, CO2, EC, water content), Rooms, Zones
- Lab Results, Test Batches, Transfers
The Trym Integration Challenge
Cultivators run daily compliance and grow operations on Trym, but turning its mobile-first, Metrc-driven workflows into API-driven automation is non-trivial:
- Mobile-first capture: Plant weights, harvest actions, and tag scans flow through the mobile app, so much of the operational data never touches a documented public endpoint
- No public developer API: Trym surfaces integrations to specific hardware and software partners, but does not publish a general-purpose, self-serve API for arbitrary data access
- Metrc as the system of record: Compliance state lives in Metrc and is mirrored into Trym, so plant, harvest, and package data must reconcile across two systems with state-specific rules
- Heterogeneous sensor sources: Aranet, Growlink, TrolMaster, and Argus each feed environmental data through their own hardware and APIs, leaving readings fragmented across vendors
- State-by-state variability: Metrc behavior, tag formats, and reporting requirements differ by state, so a single integration must handle multiple traceability configurations
- Authentication for automation: Account login and session handling complicate headless, scheduled data access for analytics and ERP sync
How Supergood Creates Trym APIs
Supergood reverse-engineers Trym's authenticated web and mobile flows to deliver a resilient API layer for your cultivation operation—covering plants, harvests, tasks, sensor data, and Metrc-synced compliance records.
- Handles account login and session continuity securely, with automated refresh and change detection
- Normalizes plant, harvest, task, and sensor responses into consistent objects so you integrate once
- Reconciles Trym data against Metrc tags and state-specific traceability rules
- Unifies environmental readings across Aranet, Growlink, TrolMaster, and Argus into a single sensor stream
Use Trym with AI agents: Trym MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your facilities, Metrc states, and connected sensor hardware.
- Supergood Generates and Validates Your API
We deliver a production-ready Trym adapter tailored to your grow operation and compliance configuration.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Trym evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Trym account and obtain a session token for downstream calls.
Cultivation
/plantsList plants with filters for batch, strain, growth phase, room, and Metrc tag status.
Harvests
/harvestsRetrieve harvests with plant weights, waste records, and associated package data.
Harvests
/record_weightRecord plant or harvest weights captured from mobile scans or Bluetooth scales.
Tasks
/tasksPull tasks, assignments, and notes across teams, rooms, and growth stages.
Sensors
/sensor_readingsFetch climate and substrate readings (temperature, humidity, CO2, EC, water content) by room and zone.
Use Cases
Sync cultivation and harvest data into your warehouse
- Pull plants, batches, and harvests with weights and waste records into a single warehouse - Stream harvest and package events to downstream BI, inventory, and ERP tools - Reconcile plant and package records against Metrc tags for unified compliance reporting
Automate Metrc compliance reconciliation
- Mirror plant, harvest, and package state between Trym and Metrc across states - Flag discrepancies between recorded weights and traceability submissions - Trigger remediation tasks when compliance records fall out of sync
Centralize sensor and crop-steering data
- Unify temperature, humidity, CO2, EC, and water-content readings across Aranet, Growlink, TrolMaster, and Argus - Correlate environmental conditions with yield and harvest outcomes - Surface out-of-range room and zone conditions to alerting workflows
Keep tasks and team activity in sync
- Pull task assignments and completion status into project and labor-tracking systems - Push new tasks and reassignments from external scheduling tools back into Trym - Report on labor hours by room, batch, and growth phase
Technical Specifications
Authentication
Account username/password handled in a managed session with secure credential storage
Connectivity
Authenticated web and mobile flows reverse-engineered into a stable API surface
Response format
Normalized JSON across Plant, Harvest, Task, Sensor, and Metrc-synced objects
Rate limits
Adaptive throttling tuned to your account to avoid platform-side limits
Session management
Automatic session refresh, re-login handling, and credential rotation
Data freshness
Near real-time pulls for plants, harvests, and sensor readings with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for harvest completion, weight capture, task updates, and sensor thresholds
Latency
Sub-second reads on cached entities; multi-second writes when posting weights and Metrc actions
Throughput
Horizontally scaled workers sized to multi-room, multi-facility cultivation volume
Reliability
Retry, backoff, and idempotency keys for weight recording and compliance submissions
Adaptation
Continuous monitoring of Trym releases, Metrc state changes, and sensor partner updates
Frequently asked questions
Yes. Supergood reconciles Trym's plant, harvest, and package records against Metrc tags, so compliance state is exposed through the same normalized API surface across the states where you operate.
Yes. Environmental and substrate readings from Aranet, Growlink, TrolMaster, and Argus are unified into a single sensor stream with temperature, humidity, CO2, EC, and water-content values by room and zone.
Trym integrates with specific hardware and software partners but does not publish a general-purpose, self-serve developer API. Supergood builds a resilient API over your authenticated Trym account so you can access any data your operation captures.
Yes. Beyond reads, the API supports actions like recording weights and creating or reassigning tasks, with idempotency and retry handling so writes stay safe across mobile-captured workflows.
Each integration is profiled against the Metrc configuration for your states, preserving state-specific tag formats and reporting rules rather than forcing a generic schema.