T3 API : Supercollections

• T3 API Supercolletions
  • What is a Supercollection?
  • Learning by example
• Next Steps

---

T3 API Supercolletions

With Metrc data, users frequently encounter these sorts of problems:

• "I want to load my packages, but also need test results for each"
• "I want to load my transfers, but also want all the packages"
• "I want to load my harvests, but I also want all the plants associated with each harvest"

Enter supercollections

What is a Supercollection?

The best way to understand supercollections is to compare them to T3 collections:

• T3 collection endpoints all are designed to send exactly one request to Metrc per request to T3.
  • Examples: Active Packages, Incoming Transfers, Active Harvests.
  • This ensures the endpoints are fast, have generous rate limits, and are flexible to use.
  • If you want to load metadata for a collection, you need to explicitly request it per row.
• T3 supercollection endpoints are designed to eagerly load all metadata for each collection object.
  • Examples: Active Superpackages, Incoming Supertransfers, Active Superharvests
  • They extend existing collection endpoint behavior.
  • This allows the endpoint to efficiently load, organize, and analyze the metadata for you.
  • Endpoints have lower rate limits, and are slower to use.
  • Metadata is loaded declaratively. For example, you'd specify you want lab results and history for an active superpackages request.

Learning by example

TODO

Next Steps

• Refer to the T3 API documentation to explore all the available endpoints.
• Most API endpoints require a T3+ subscription. If you don't have a T3+ subscription, you can sign up here.