{ "data": [ { "label": "1A4000000000000000000001", "item": { "name": "Pineapple Express Flower" }, "quantity": 1130.7, "unitOfMeasureAbbreviation": "g", "metadata": { "indexedLabResults": { "totalTHC": { "full": "Total THC: 22.4 %", "name": "Total THC", "value": 22.4, "unit": "%" }, "totalCBD": { "full": "Total CBD: 0.1 %", "name": "Total CBD", "value": 0.1, "unit": "%" }, "topTerpene1": { "full": "Myrcene: 1.2 %", "name": "Myrcene", "value": 1.2, "unit": "%" } } } } ] }
Lab result keys are normalized across every state: "Total THC" and "Total Delta-9 THC" both come back as totalTHC.
Case study
When a data-entry role went unfilled, Nuthera automated its Metrc reconciliation with the T3 API and Google Sheets. Then it went further, tracing the true cost of every Metrc tag it has ever created, down to the batch.
Read the Nuthera case study →“With T3, I completed something no other ERP company in cannabis has shown me: the true input and output cost of every Metrc tag we have ever made.”

Building directly on the Metrc API means handling per-state differences, credentials, and data stitching yourself. The T3 API gives you programmatic access to the same Metrc data without any of that.
The T3 API is independent of the Metrc API: it does not use Metrc API keys and is not affiliated with Metrc.
The T3 API is plain REST and JSON, so it works from any language. Python developers can also use the t3api and t3api-utils libraries.
Sign up on the T3 dashboard at dash.trackandtrace.tools.
Create a T3 secret key and store it as T3_API_KEY.
Call any endpoint. Responses are paginated JSON with page, pageSize, total, and data.
curl "https://api.trackandtrace.tools/v2/packages/active?licenseNumber=LIC-000123" \ -H "X-T3-API-Key: $T3_API_KEY"
Metrc's own API is difficult to work with: inconsistent across states, thin on documentation, and tedious to page through. The T3 API is an independent alternative that makes working with your Metrc data fast and predictable.
Metrc behaves differently in every state it operates in. The T3 API normalizes those differences behind a single, consistent REST interface, so the integration you build works the same whether a license lives in California, Michigan, or anywhere else Metrc runs.
Interactive OpenAPI documentation with real request and response examples for every endpoint, predictable JSON shapes, consistent pagination, and standard bearer or secret-key authentication. Developers can go from reading a page to a working call in minutes.
Hundreds of endpoints spanning the entire Metrc data model—not just the handful most tools expose. Read inventory, write transfers, generate labels, pull lab results, and automate workflows that previously required manual data entry in the Metrc UI.
Pull entire Metrc datasets in a single request instead of paging through hundreds of calls. Super Reports join related records—packages with items, harvests with their packages—into clean, flat tables ready for analysis, and Spreadsheet Sync keeps Google Sheets and Excel up to date automatically.
If Metrc tracks it, the T3 API can reach it. Endpoints span every major area of the platform:
Plants, plant batches, and harvests across every growth phase.
Processing jobs, package creation, and testing workflows.
Incoming, outgoing, rejected, and hub transfers with manifests.
Lab results, testing states, and result documents.
Active, inactive, in-transit, and on-hold packages.
Full product catalog and strain database.
Available, used, and voided tags, plus tag orders.
Generate print-ready label PDFs on demand.
The T3 API turns Metrc from a compliance chore into programmable infrastructure. A few of the things teams build with it:
Pull the exact datasets auditors ask for on a schedule, instead of exporting spreadsheets by hand.
Keep ERP, POS, and internal databases in step with Metrc inventory in near real time.
Feed live Metrc data into reporting tools to track yield, sales, and movement across licenses.
Create transfers, generate labels, and write back to Metrc from the tools teams already use.
A limited set of endpoints is free for anyone with a Metrc login. Full API access, Super Reports, and Spreadsheet Sync are included with a T3+ subscription. Explore the tiers to find the right fit.
View T3+ PlansCommon questions about working with the Metrc API.
The Metrc API is the programmatic interface for reading and writing cannabis track-and-trace data in Metrc. The T3 API is a separate, developer-friendly alternative: it gives you programmatic access to the Metrc data available to you on metrc.com, with consistent JSON responses and interactive documentation across every Metrc state. It does not use Metrc API keys and is not affiliated with Metrc.
Metrc offers its own API for third-party software integrators. The T3 API is an independent REST API that reaches the same Metrc data without Metrc API keys, so one integration works the same regardless of which state a license operates in.
Generate a T3 secret key and send it in the X-T3-API-Key header, or exchange your credentials for a short-lived bearer token. From there you can pull inventory, create transfers, generate labels, and read lab results with a single REST call. Full examples are in the interactive API documentation.
Yes. The T3 API covers every state where Metrc operates and normalizes per-state differences behind one consistent interface, so your code does not change from state to state.
Teams use the T3 API to automate compliance reporting, sync Metrc inventory with ERP and POS systems, power BI dashboards, generate compliance labels, and build custom integrations that read from and write back to Metrc.
A limited set of T3 API endpoints is free for anyone with a Metrc login. Full access to the T3 API, Super Reports, and Spreadsheet Sync is included with a T3+ subscription.