npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

metrc

v0.0.9

Published

Interact with the Metrc API from your Node application

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

toddruntoddrun

Keywords

metrc

Readme

Metrc Wrapper - interact with Metrc in your Node application

Interacting with Metrc's API requires certification. You'll need API keys to use the library.

What the heck is Metrc anyway???

Metrc is the Cannabis Tracking System (CTS) used in most States where recreational cannabis is legal (and even in some that still only offer Medical Marijuana). Metrc is built and maintained by Franwell Inc., and is only accessible to licensees, verified integrators and other authorized entities.

What's the Metrc API?

While Metrc includes a Web based interface for licensess to interact with, it also includes an API to allow software vendors to programmatically update Metrc data. The API does not necassarily provide all of the functionality of the Web based interface, but is the only way 3rd parties can report data into Metrc.

Why can't I just start using the API? What possible benefit could this open source project provide?

Every software vendor in the Cannabis space is currently writing their own code for accessing and interacting with the Metrc API. This library is not intended to be a production ready replacement for writing your own code (though you're welcome to use it). It provides a partial implementation to highlight some of the peculiarities others have encountered, hopefully saving some of your sanity in the process.

For example, when you POST a new record, the API returns a status code of 200 . . . and that's it. Since you'll likely need to determine the "Id" of the record you just created, an empty response payload is less than optimal. So, this library wraps each POST with a corresponding GET, and logic to extract the newly introduced record. Likewise, the GET endpoints force you to page through data based on the "LastModified" field, and only allow a short time span (beginning 4/1/2018 requests are limited to no more than a 24 hour period). This library provides a way to make multiple calls in a single method call (though be careful . . . call limits and throttling rules are always subject to change and could cause issues).