OpenTHC API: The Backbone of Cannabis Traceability

You can think of Application Programming Interfaces (API) like old switchboard operators. Human operators once connected telephones manually before technology became automated for quicker communication. An API platform is like switchboard automation. Only instead of connecting peoples’ voices; APIs connect types of data between computers.

APIs exist for all sorts of software. Have you ever clicked on a webpage that doesn’t load? The problem could be rooted in how that website’s API communicates to your browser. APIs make all kinds of transactions happen through some kind of technology. The OpenTHC platform moves businesses towards a common API for the cannabis industry.

The design of OpenTHC API uses decentralized applications for seamless reporting. This enables traceability reporting between different businesses, or to state and local regulatory platforms. Done from about anywhere with a steady wi-fi signal. Importantly, the OpenTHC API is flexible enough to function on different pieces of technology. From different manufacturers’ smartphones, to tablets, or personal computers. Everyone in the licensed operator can upload and report their business activity.

The OpenTHC team built the OpenTHC API alongside open-source contributors. The API and the data model govern all operations between internal and external services in the operating environment. The OpenTHC platform features several applications for reporting between businesses and government agencies. We call these ‘service' applications. Operators and governments can use these apps off-the-shelf. Or, these apps may serve as reference implementations. In either case, the underlying API structure remains the same.

Each component of the API acts as a definition to the objects tracked in that environment. API objects cover regulated material and core identity definitions. Tracked transactions get reported by linking core identity and regulated material together. API objects have corresponding operation resources representing required traceability reporting actions. Moreover, data validation occurs on each API operation any time a request gets made. In the event of failed requests, rejected request include clear, contextual errors.

OpenAPI specifications for governance give government officials ways to update or improve requirements. Standard versioning means regulators can communicate changes in requirements to all businesses.

OpenTHC API is the automated switchboard of cannabis traceability. A secure hub linking business activities and transactions while reporting needed information. Learn more about our API manual, or from the OpenTHC Documentation.

Questions? Want to try self-hosting the OpenTHC platform? Don’t hesitate to reach out to the OpenTHC team!