## WHAT IS THIS? This API is part of the [Track & Trace Tools](https://trackandtrace.tools) platform. The API allows you to programmatically access all your Metrc data that is available on metrc.com It is not related to the Metrc 3rd party API, does not use Metrc API keys, and is not affiliated with Metrc. If you're looking for where to get started, check out the [T3 Wiki API Getting Started guide](https://github.com/classvsoftware/t3-wiki/wiki/T3-API-:-Getting-Started). The T3 API is subject to the [Track & Trace Tools Terms of Use](https://www.trackandtrace.tools/terms-of-use). ## FREE API ACCESS (LIMITED) The T3 API features a limited number of free endpoints available to anyone with a Metrc login. These can be found in the [Free](#/Free) section. ## FULL API ACCESS There are two ways to get premium access to the T3 API: - **Subscribe to [T3+](https://trackandtrace.tools/plus)** *OR* - **Use a provided T3 API key (consulting clients only. [Reach out](mailto:matt@trackandtrace.tools) for more information.)** ## AUTHENTICATION The T3 API uses JSON Web Tokens (JWT) for request authentication. To obtain a JWT, use one of the following: - **metrc.com login credentials:** - **hostname**: (The website you use to login to metrc: `ca.metrc.com`, `or.metrc.com`, etc.) - **username**: Your Metrc username - **password**: Your Metrc password - **otp**: A one-time password used for 2-factor authentication (Only applies to Michigan users) *OR* - **T3 API key** Refer to the **Authentication** endpoints below for more information. ## SECRET KEYS Some endpoints support the use of secret key authentication. This allows you to use simple URLs to access your Metrc data. ### Usage Pass the `secretKey` returned from the request in the query string: `?secretKey=<yourSecretKeyGoesHere>` ### Generating Secret Keys Refer to the [/v2/auth/secretkey](#/Authentication/post_v2_auth_secretkey) endpoint for information on generating secret keys. [Secret Key Generation Tool](/v2/pages/secret-key) [Sync Link Creation Tool](/v2/pages/sync-link) ## SECURITY The T3 API interacts with Metrc in a similar manner to the [Track & Trace Tools](https://chromewebstore.google.com/detail/track-trace-tools/dfljickgkbfaoiifheibjpejloipegcb) Chrome extension. The API login process is designed with a strong emphasis on security. Your Metrc login details are never stored, and the API backend employs robust encryption methods to protect your temporary Metrc session. ### Key Security Measures: - **Single-Use Login Credentials:** - The T3 API uses your login credentials only once to authenticate with Metrc. - After the Metrc login process is complete, your login credentials are immediately deleted from the system. - You are required to enter your login credentials each time you access the T3 API, ensuring that your credentials are never stored. - **Secure Temporary Session Storage:** - The T3 API securely encrypts your logged-in Metrc session data. This data is only used when you make requests through the T3 API. - The encrypted session data is automatically deleted after 24 hours, ensuring that your session information is not retained longer than necessary. For any questions or concerns, please contact [matt@trackandtrace.tools](mailto:matt@trackandtrace.tools). ## PRIVACY The T3 API privacy model follows the same principles as the [Track & Trace Tools](https://chromewebstore.google.com/detail/track-trace-tools/dfljickgkbfaoiifheibjpejloipegcb) Chrome extension. The T3 API functions solely as a connector between you and Metrc, ensuring your privacy is protected. - **No Data Collection:** - The T3 API does not record, save, harvest, inspect, or analyze any of your data. - All data interactions are ephemeral and occur in real-time, without permanent storage. - **Secure and Private Access:** - Your data is never shared with third parties. Unauthorized access to your login information or data is strictly prohibited. - T3 employs industry-standard encryption protocols to safeguard all communications between the T3 API and Metrc. - **User-Controlled Sessions:** - Your Metrc login credentials and session are used exclusively by you. The T3 API will never initiate Metrc traffic without your explicit authorization. - **Compliance and Best Practices:** - T3's privacy practices are aligned with applicable data protection regulations, including GDPR and CCPA, ensuring that your data rights are respected. The T3 API is subject to the [Track & Trace Tools Privacy Policy](https://trackandtrace.tools/privacy-policy). For any privacy-related inquiries, please contact [matt@trackandtrace.tools](mailto:matt@trackandtrace.tools). ## PERMISSIONS Each Metrc account has different permissions based on several factors: - Permissions granted by your Metrc admin - Class of license (manufacturing, cultivation, etc) - US state the license operates in Use the Permissions endpoints to determine which actions are available to you. ## LICENSES View a list of all licenses available to the current user: `GET https://api.trackandtrace.tools/v2/licenses` Only one license can be queried per request. Specify the target license with the required `licenseNumber` query parameter: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001` ## RATE LIMITING The API has a global default request rate limit of 600 requests/minute/user. Some routes have lower rate limits. ## COLLECTIONS All data is queried as collections. There are no individual object endpoints. For example, you cannot find an individual object using an endpoint like `/plants/{plantId}`, individual objects must be queried by filtering the collection endpoint `/plants` for the exact `plantId`. Collections are paginated, and can be filtered and sorted by individual object fields. The JSON response object includes the following properties: - `data`: An array of objects, or any empty array - `page`: The requested page index - `pageSize`: The requested page size - `total`: The total number of items in this collection. Use this to determine how many pages are required to return the entire collection. ### COLLECTION PAGINATION Metrc data collections are queried as pages. Use the `page` and `pageSize` query parameters to indicate which page should be returned. By default, `page=1` and `pageSize=100`. Example: Return page 3 with a page size of 500: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001&page=3&pageSize=500` ### COLLECTION SORTING Metrc data collections can be sorted. Use the `sort` query parameter to indicate how the collection should be sorted. Example: Sort items by `name` descending: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001&sort=name:desc` ### COLLECTION FILTERING Metrc data collections can be filtered. Use one or more `filter` query parameters to indicate how filters should be applied. Example: Filter items that contain \"flower\" in the `name` field: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001&filter:name__contains=flower` Multiple filters can be applied, and you can specify the logical operator (defaulting to \"and\"): Example: Filter items that contain \"flower\" in the `name` field OR \"kush\" in the `name` field: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001&filter=name__contains:flower&filter=name__contains:kush&filterLogic=or` #### FILTERING STRINGS String fields support the following filter operators: - `contains` - `doesnotcontain` - `eq` - `neq` - `startswith` - `endswith` Example `?filter=name__contains:flower` **Note: all string filters are case-insensitive** #### FILTERING DATETIMES Datetime fields support the following filter operators: - `lt` - `lte` - `eq` - `neq` - `gt` - `gte` Example: `?filter=harvestedDate__gte:2024-07-17T20:26:07.117Z` **Note: all datetime filters use ISO8601 datetimes** #### FILTERING BOOLEANS Boolean fields support the following filter operators: - `eq` Example: `?filter=finished__eq:true` ### LOADING FULL COLLECTIONS `pageSize` is limited to 500 in most cases, so you may need to load multiple pages if a license has a large number of packages. Refer to [this example](https://github.com/classvsoftware/t3-api/blob/master/load_all_active_packages.py) for how to load a full collection in a python script. ## USING THE API The API can be used in any way you like, but writing simple scripts to accomplish common tasks is an excellent way to take advantage of it. The full OpenAPI spec, which can be imported into Postman, can be found here: [/v2/spec/openapi.json](/v2/spec/openapi.json) [**Lots** of example scripts that show how the use the T3 API can be found here](https://github.com/classvsoftware/t3-api) ## CONTACT - **Responsible Organization:** Class V LLC - **Responsible Developer:** Matt Frisbie - **Email:** [matt@trackandtrace.tools](mailto:matt@trackandtrace.tools) - **URL:** [https://trackandtrace.tools](https://trackandtrace.tools) - **Terms of Use:** [https://www.trackandtrace.tools/terms-of-use](https://www.trackandtrace.tools/terms-of-use)
Raw data
{
"_id": null,
"home_page": null,
"name": "t3api",
"maintainer": null,
"docs_url": null,
"requires_python": null,
"maintainer_email": null,
"keywords": "OpenAPI, OpenAPI-Generator, T3 API",
"author": "OpenAPI Generator community",
"author_email": "team@openapitools.org",
"download_url": "https://files.pythonhosted.org/packages/ec/ce/392ffb587c297d60ca9f35016a90bb4f87c0d90fd2f8f2a5cf9a91ac5258/t3api-0.6.0.tar.gz",
"platform": null,
"description": " ## WHAT IS THIS? This API is part of the [Track & Trace Tools](https://trackandtrace.tools) platform. The API allows you to programmatically access all your Metrc data that is available on metrc.com It is not related to the Metrc 3rd party API, does not use Metrc API keys, and is not affiliated with Metrc. If you're looking for where to get started, check out the [T3 Wiki API Getting Started guide](https://github.com/classvsoftware/t3-wiki/wiki/T3-API-:-Getting-Started). The T3 API is subject to the [Track & Trace Tools Terms of Use](https://www.trackandtrace.tools/terms-of-use). ## FREE API ACCESS (LIMITED) The T3 API features a limited number of free endpoints available to anyone with a Metrc login. These can be found in the [Free](#/Free) section. ## FULL API ACCESS There are two ways to get premium access to the T3 API: - **Subscribe to [T3+](https://trackandtrace.tools/plus)** *OR* - **Use a provided T3 API key (consulting clients only. [Reach out](mailto:matt@trackandtrace.tools) for more information.)** ## AUTHENTICATION The T3 API uses JSON Web Tokens (JWT) for request authentication. To obtain a JWT, use one of the following: - **metrc.com login credentials:** - **hostname**: (The website you use to login to metrc: `ca.metrc.com`, `or.metrc.com`, etc.) - **username**: Your Metrc username - **password**: Your Metrc password - **otp**: A one-time password used for 2-factor authentication (Only applies to Michigan users) *OR* - **T3 API key** Refer to the **Authentication** endpoints below for more information. ## SECRET KEYS Some endpoints support the use of secret key authentication. This allows you to use simple URLs to access your Metrc data. ### Usage Pass the `secretKey` returned from the request in the query string: `?secretKey=<yourSecretKeyGoesHere>` ### Generating Secret Keys Refer to the [/v2/auth/secretkey](#/Authentication/post_v2_auth_secretkey) endpoint for information on generating secret keys. [Secret Key Generation Tool](/v2/pages/secret-key) [Sync Link Creation Tool](/v2/pages/sync-link) ## SECURITY The T3 API interacts with Metrc in a similar manner to the [Track & Trace Tools](https://chromewebstore.google.com/detail/track-trace-tools/dfljickgkbfaoiifheibjpejloipegcb) Chrome extension. The API login process is designed with a strong emphasis on security. Your Metrc login details are never stored, and the API backend employs robust encryption methods to protect your temporary Metrc session. ### Key Security Measures: - **Single-Use Login Credentials:** - The T3 API uses your login credentials only once to authenticate with Metrc. - After the Metrc login process is complete, your login credentials are immediately deleted from the system. - You are required to enter your login credentials each time you access the T3 API, ensuring that your credentials are never stored. - **Secure Temporary Session Storage:** - The T3 API securely encrypts your logged-in Metrc session data. This data is only used when you make requests through the T3 API. - The encrypted session data is automatically deleted after 24 hours, ensuring that your session information is not retained longer than necessary. For any questions or concerns, please contact [matt@trackandtrace.tools](mailto:matt@trackandtrace.tools). ## PRIVACY The T3 API privacy model follows the same principles as the [Track & Trace Tools](https://chromewebstore.google.com/detail/track-trace-tools/dfljickgkbfaoiifheibjpejloipegcb) Chrome extension. The T3 API functions solely as a connector between you and Metrc, ensuring your privacy is protected. - **No Data Collection:** - The T3 API does not record, save, harvest, inspect, or analyze any of your data. - All data interactions are ephemeral and occur in real-time, without permanent storage. - **Secure and Private Access:** - Your data is never shared with third parties. Unauthorized access to your login information or data is strictly prohibited. - T3 employs industry-standard encryption protocols to safeguard all communications between the T3 API and Metrc. - **User-Controlled Sessions:** - Your Metrc login credentials and session are used exclusively by you. The T3 API will never initiate Metrc traffic without your explicit authorization. - **Compliance and Best Practices:** - T3's privacy practices are aligned with applicable data protection regulations, including GDPR and CCPA, ensuring that your data rights are respected. The T3 API is subject to the [Track & Trace Tools Privacy Policy](https://trackandtrace.tools/privacy-policy). For any privacy-related inquiries, please contact [matt@trackandtrace.tools](mailto:matt@trackandtrace.tools). ## PERMISSIONS Each Metrc account has different permissions based on several factors: - Permissions granted by your Metrc admin - Class of license (manufacturing, cultivation, etc) - US state the license operates in Use the Permissions endpoints to determine which actions are available to you. ## LICENSES View a list of all licenses available to the current user: `GET https://api.trackandtrace.tools/v2/licenses` Only one license can be queried per request. Specify the target license with the required `licenseNumber` query parameter: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001` ## RATE LIMITING The API has a global default request rate limit of 600 requests/minute/user. Some routes have lower rate limits. ## COLLECTIONS All data is queried as collections. There are no individual object endpoints. For example, you cannot find an individual object using an endpoint like `/plants/{plantId}`, individual objects must be queried by filtering the collection endpoint `/plants` for the exact `plantId`. Collections are paginated, and can be filtered and sorted by individual object fields. The JSON response object includes the following properties: - `data`: An array of objects, or any empty array - `page`: The requested page index - `pageSize`: The requested page size - `total`: The total number of items in this collection. Use this to determine how many pages are required to return the entire collection. ### COLLECTION PAGINATION Metrc data collections are queried as pages. Use the `page` and `pageSize` query parameters to indicate which page should be returned. By default, `page=1` and `pageSize=100`. Example: Return page 3 with a page size of 500: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001&page=3&pageSize=500` ### COLLECTION SORTING Metrc data collections can be sorted. Use the `sort` query parameter to indicate how the collection should be sorted. Example: Sort items by `name` descending: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001&sort=name:desc` ### COLLECTION FILTERING Metrc data collections can be filtered. Use one or more `filter` query parameters to indicate how filters should be applied. Example: Filter items that contain \\"flower\\" in the `name` field: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001&filter:name__contains=flower` Multiple filters can be applied, and you can specify the logical operator (defaulting to \\"and\\"): Example: Filter items that contain \\"flower\\" in the `name` field OR \\"kush\\" in the `name` field: `GET https://api.trackandtrace.tools/v2/items?licenseNumber=LIC-00001&filter=name__contains:flower&filter=name__contains:kush&filterLogic=or` #### FILTERING STRINGS String fields support the following filter operators: - `contains` - `doesnotcontain` - `eq` - `neq` - `startswith` - `endswith` Example `?filter=name__contains:flower` **Note: all string filters are case-insensitive** #### FILTERING DATETIMES Datetime fields support the following filter operators: - `lt` - `lte` - `eq` - `neq` - `gt` - `gte` Example: `?filter=harvestedDate__gte:2024-07-17T20:26:07.117Z` **Note: all datetime filters use ISO8601 datetimes** #### FILTERING BOOLEANS Boolean fields support the following filter operators: - `eq` Example: `?filter=finished__eq:true` ### LOADING FULL COLLECTIONS `pageSize` is limited to 500 in most cases, so you may need to load multiple pages if a license has a large number of packages. Refer to [this example](https://github.com/classvsoftware/t3-api/blob/master/load_all_active_packages.py) for how to load a full collection in a python script. ## USING THE API The API can be used in any way you like, but writing simple scripts to accomplish common tasks is an excellent way to take advantage of it. The full OpenAPI spec, which can be imported into Postman, can be found here: [/v2/spec/openapi.json](/v2/spec/openapi.json) [**Lots** of example scripts that show how the use the T3 API can be found here](https://github.com/classvsoftware/t3-api) ## CONTACT - **Responsible Organization:** Class V LLC - **Responsible Developer:** Matt Frisbie - **Email:** [matt@trackandtrace.tools](mailto:matt@trackandtrace.tools) - **URL:** [https://trackandtrace.tools](https://trackandtrace.tools) - **Terms of Use:** [https://www.trackandtrace.tools/terms-of-use](https://www.trackandtrace.tools/terms-of-use) \n \n",
"bugtrack_url": null,
"license": null,
"summary": "T3 API",
"version": "0.6.0",
"project_urls": null,
"split_keywords": [
"openapi",
" openapi-generator",
" t3 api"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "1292109ef7a5a41730ae7753282b1a90355004ad82cc1f8693a9d5d000256abd",
"md5": "1203da2e904dfcc4b3b39987a35bd7c9",
"sha256": "f23179818f28f7aa4677d46d0f4e5a9af45c1ca67da19d1ce7a8e4b0d70d9a28"
},
"downloads": -1,
"filename": "t3api-0.6.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "1203da2e904dfcc4b3b39987a35bd7c9",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": null,
"size": 1271653,
"upload_time": "2025-07-21T15:43:00",
"upload_time_iso_8601": "2025-07-21T15:43:00.001738Z",
"url": "https://files.pythonhosted.org/packages/12/92/109ef7a5a41730ae7753282b1a90355004ad82cc1f8693a9d5d000256abd/t3api-0.6.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "ecce392ffb587c297d60ca9f35016a90bb4f87c0d90fd2f8f2a5cf9a91ac5258",
"md5": "872be2cc96e0f13bc51828e7f8b70aa5",
"sha256": "e60d07367f070897ae7c8311c7bebadccf3277e9a68c5f0f020bc8a448ef930e"
},
"downloads": -1,
"filename": "t3api-0.6.0.tar.gz",
"has_sig": false,
"md5_digest": "872be2cc96e0f13bc51828e7f8b70aa5",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 499638,
"upload_time": "2025-07-21T15:43:01",
"upload_time_iso_8601": "2025-07-21T15:43:01.431217Z",
"url": "https://files.pythonhosted.org/packages/ec/ce/392ffb587c297d60ca9f35016a90bb4f87c0d90fd2f8f2a5cf9a91ac5258/t3api-0.6.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-07-21 15:43:01",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "t3api"
}
JSON