Washington BioTrackTHC QA Results Bug #6

Here is a pretty serious bug in the Washington State Traceabilty system that is powered by BioTrackTHC. In the object descriptors provided by the BioTrack API there is a field called ‘sessiontime’. This value is populated with the time the object was last modified, generally. On the QA results API calls however this field is […]

Published: March 29, 2017
Categories: API

BioTrackTHC User Account Bugs

There is a huge bug in the BioTrackTHC API in Washington (and NM, HI, IL). We’ve raised this issue with both the WSLCB and with BioTrack and yet BioTrackTHC refuses to address the issue at all. Even worse, if you are affected by the bug BioTrackTHC refuses to help. Reproduction: From the BioTrack API it’s […]

Published: February 20, 2017
Categories: API
Tags: , ,

Data Anomaly in Public Records

Through the Freedom of Information Act we are able to obtain database dumps from the Washington State BioTrack database. Here’s a small anomaly we’ve noticed on this one. Keep in mind, this is a system that is supposed to guarantee unique identifiers for all plants and inventory and provide robust tracking. select id from inventory […]

Published: October 27, 2016
Categories: Technology

BioTrack/WA – Phantom Inventory on Adjustments & Derivatives

Yet another data inconsistency in the BioTrackTHC system for Washington State.  In this case we see the system indicate an Inventory Adjustment – but there is no corresponding record to the Inventory itself.  Either the original Inventory records have been dropped from sync, or the Adjust data-set is improperly including this one. { “atype”: 4, “inventoryid”: […]

Published: October 17, 2016
Categories: Marijuana Regulation

BioTrackTHC Cross-State Data Contamination

Today we’ve observed some serious issues with the BioTrackTHC API in New Mexico.  These issues clearly indicate their system is not tested or audited for integrity.  If BioTrackTHC cannot tell the difference between New Mexico and Washington State how can we trust the other data in their system to properly track marijuana? Manifest with Orphaned […]

Published: September 29, 2016
Categories: Marijuana Regulation

BioTrack API Update 1.18 – Another Fail

Today BioTrackTHC+WSLCB released another update to the API; again with zero advance notice for third party integrators.  At the end of Friday an announcement was provided which details the changes.  This leaves integrators (such as WeedTraQR) in the lurch.  Now, we have to work through the weekend to integrate these critical updates. On multiple occasions […]

Published: June 25, 2016
Categories: API, Traceability, Transparency

BioTrackTHC API Security is a Fucking Joke

The authentication system for this API is a fucking joke. Rather than use established standards like oAuth or hash-tokens they require that users of the API use the SAME CREDENTIALS that are used to sign-in to their system. This is a KNOWN ANTI-PATTERN in the technical world for many reasons. It’s problematic because it requires […]

Published: June 1, 2016
Categories: API, Traceability

BioTrackTHC API – Abrupt Change, Bad Documentation

BioTrackTHC abruptly changed their API On Saturday, May 28th with zero notice to any of the third party integrators in Washington State. The change this time created a new value for the LocationType field of the Vendor objects. The new value is ‘9’. BioTrackTHC also (silently) published an updated API document (https://biotrackthc.com/sites/default/files/state-docs/JSON-21.pdf). This new documentation […]

Published: June 1, 2016
Categories: API, Technology, Traceability

BioTrackTHC API – License Handling Modified w/o Notice

Once again BioTrackTHC has modified their API with zero notice to the third party integrator. The API in question this time is inventory_manifest_lookup. This API takes only one parameter, a six digit license ID. Prior to May 14th, if one was to query this API using an in-active license ID it would respond with the […]

Published: May 19, 2016
Categories: API, Traceability

BioTrackTHC Washington – QA Results Crazy!

There appears to be a bit of a discrepancy with how the BioTrackTHC system handles the QA results. Sometimes it shows the results are there and keeps the association with the parent ID. In other cases that relationship seems to be lost and one must know a sub-lot of a sub-lot ID to find the […]

Published: May 18, 2016
Categories: API, Traceability