GrowFlow users within Metrc jurisdictions can have their actions reported to Metrc using a global Metrc API key that identifies the Metrc Admin user for the license or can configure a personal Metrc API key under User Settings. The API key is what is used to communicate to Metrc which users made any updates to their Metrc data by way of GrowFlow. Auditors might check logs to see which users are making changes, and they may expect a reasonable distribution of users across these logs.
We now have a feature that allows users to have actions reported under their own API key so that not all GrowFlow changes are associated with a single global API key/user.
There are two sections to this help article that you can skip to by clicking the section title below:
A. Finding and using your global API key
Log in to METRC with your Metrc Admin user's username and password.
2. Click on the user ID in the top right-hand corner of the screen.
3. On the dropdown menu, click "API keys".
4. On the API Keys page, your API key will populate in the box under Programmatic Access. If you do not see a number in the box, click "generate". You will also want to generate a new API key if you are experiencing errors with permissions in your GrowFlow account.
If you reset your API key by pressing "Generate" the new API key will need to be inserted into all your accounts. If you have many accounts, please contact support for help with managing your API keys
5. Now that you have your API key, you will need to copy and then paste it into your GrowFlow account.
On your Metrc API key page, start copying the text above "API Keys", this will allow you to capture the entire key on your clipboard.
Open your GrowFlow account and go to Account Settings:
Here, you will paste your API key into the box provided under Traceability Credentials
Click "Update Traceability Credentials"
B. Using your personal user API key
Important: You must first be set up by your Metrc Admin user as a licensed employee user in your Metrc account and given permissions in the Metrc account before you complete the steps below.
Log in to Metrc with your own user credentials
Click on your user ID in the top right-hand corner of the screen
On the dropdown menu, click "API keys"
On the API Keys page, your API key will populate in the box under Programmatic Access.
If you do not see a number in the box, click "generate". You will also want to generate a new API key if you are experiencing errors with permissions in your GrowFlow account.
Copy the API Key
Go to your GrowFlow account tab, click on your account name in the upper right and select "User Settings" :
In the window called "Manage your GrowFlow User Profile":
User API Key - Select this option to use your own Metrc API Key
Once input, you will see the option to Test Connection - you must press this to confirm the key is valid
If valid, GF will display all the licenses that this API Key can be applied to for step 3 below; ideally, this will be all licenses in your organization that were set up in GrowFlow that you have user access to, so that you can adjust your API key settings once
Global API Key - If this is selected, the user will continue to use the global API Key to submit all updates to Metrc
Update key to all licenses you have access to - If this option is selected, then the API Key saved in step 1 immediately above will be applied to all licenses the key can be applied to, i.e. the User Settings will be adjusted across all of those instances of GF
Update Key - Must press this to save the Metrc API Key changes
C. Notes about a Failed Connection
GrowFlow checks all API Keys daily to ensure they are still valid. If a User API Key is found to be invalid during these checks, we'll notify the user via a non-dismissable banner:
The user must adjust their API Key under their User Settings to either update their User API Key with a valid key or switch to the Global API Key. It will not automatically switch to the global API key.
Note this behavior will only be initiated during the daily API key check; if an API becomes invalid mid-day, Metrc access will fail and permission errors will be raised to the user attempting to perform actions involving Metrc, but the banner will not be raised.