Cova API Developers Portal
Frequently Asked Questions
Last update: June 2023
How do I generate an Access Token?
In order to make authorized requests to Cova APIs, you must supply an access token to each request. This request below will allow you to use the access credentials you received in your onboarding package to get or refresh an access token.
POST https://accounts.iqmetrix.net/v1/oauth2/token
REQUEST BODY SCHEMA:
"grant_type": "password",
"username": "Username given to you in the Onboarding Package",
"password": "Password from your Onboarding Package",
"client_id": "Client Id given to you in the Onboarding Package",
"client_secret": "Client Secret given to you in the Onboarding Package"
How long is the Access Token valid For? Do we need to keep using it till it expires to minimize the call for Access Token?
The Access Token is valid for 43200 seconds (about 12 hours). You will need to re-generate an access token after every 12hours
When creating orders via the API, I am getting an error: “The integrator id is not valid, please provide a valid one.” How do I get an integrator id?
Please email apisupport@covasoftware.com to request an integrator id for you and we will be able to generate one for you, please be sure to include whether you will use this integrator id for online or in-store orders and the company name and integrator.
Are there any notifications on the POS when an order is successfully placed?
Prior to Cova POS version 1.5.x there were no incoming order notifications directly on the POS devices themselves. As of this version, dispensaries can choose to enable order notifications (both visual and auditory). The support document which outlines this process can be accessed by Cova businesses here: Online Order Notifications. There is no integrator work required to enable order notifications, they will occur automatically if the dispensary has them enabled.
Do you validate orders for compliance with purchase limits within a given market?
At this time the logic for purchase limits exists only on the point of sale itself. If an order is submitted that is over the purchase limit for that market, the user of the POS will be notified in app. We are working toward providing purchase limit validation endpoints for integrators but they are not available yet.
Do you provide WebHooks of any kind?
Not at this time.
I am encountering a 500 Internal Server Error when calling an API endpoint. What should I do?
500 Server Errors are typically the result of a server-side timeout, but can occur for a variety of reasons, and tend to be slightly more common with Bulk API Calls.
Integrator's code should handle non-sucess status codes (400+) and implement retries. Often issues are transient and can be resolved by trying later.
In the event that you encounter a 500-level error in your interaction with the API, please contact us at apisupport@covasoftware.com describing the error, please include all the API endpoints with body parameters etc.
I am working with an Integration partner, and we are having some issues with the integration. Recently added/updated products are not syncing correctly, and inventory is not correct. What Should I do?
In this case, please verify if your credentials are working correctly, you could do this by calling our API authentication endpoint or by signing into https://hub.covasoft.net/ If you are able to log in or generate an access token that means your credentials are correct and you will have to contact your integration partner. If not, please contact us at apisupport@covasoftware.com please include your credentials in the ticket.