Green Check Verified Service Provider API
The Service Provider API from Green Check Verified — 7 operation(s) for service provider.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/green-check-verified-service-provider-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Green Check Access Service Provider API
version: 1.0.0
description: Green Check Access
contact: {}
servers:
- url: https://sandbox-api.greencheckverified.com
description: Sandbox server
- url: https://prod-api.greencheckverified.com
description: Production server
tags:
- name: Service Provider
paths:
/service-providers/{sp_id}:
get:
operationId: get-service-provider
responses:
'200':
description: Ok
content:
application/json:
schema:
$ref: '#/components/schemas/ServiceProvider'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/UnauthorizedError'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/ForbiddenError'
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/NotFoundError'
'422':
description: Validation Failed
content:
application/json:
schema:
$ref: '#/components/schemas/ValidateError'
summary: Get service provider
tags:
- Service Provider
security:
- access_auth:
- service-provider:read
- admin
parameters:
- description: Service Provider Id
in: path
name: sp_id
required: true
schema:
type: string
pattern: ^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$
/service-providers/{sp_id}/crbs:
get:
operationId: get-service-provider-crbs
responses:
'200':
description: Ok
content:
application/json:
schema:
$ref: '#/components/schemas/ServiceProviderCrbs'
examples:
Example 1:
value:
nisi_2:
pos_configs:
- name: Dutchie Wholesale
status: Connected
updated_date: '2023-10-31T15:21:57.000Z'
org_type: muo
business_type: wholesale
template_id: 5d53d7a2-2D86-c5Cb-8F2e-541dcD31a3cB
template_result_id: 6622efbD-aAdb-ff0b-58C2-ebB4C9D972fc
status: bank_approved
mailing_street_address: 161 Main St
mailing_city: Chicago
mailing_state: WA
mailing_postal_code: '97201'
established_date: '2022-02-02T00:00:00.000Z'
ftEmployees: null
ptEmployees: 6
entityType: sole
dba: Green Check Dispensary
monthlySales: '20000'
monthlyCustomers: 2500
id: CdCFCfEF-ebdf-0578-a5bF-713c66B43e11
name: Dispensary1
street_address: 78685 Ben Harbor
street_address_2: Suite 901
city: North Annamae
ein: 55-5555555
phone_number: (555) 555-5555
postal_code: '55437'
country: unitedstates
state: SC
website: null
timezone: America/Juneau
pariatur3c_:
pos_configs:
- name: GrowFlow
status: Needs Attention
updated_date: '2023-10-31T15:18:22.000Z'
- name: Proteus420
status: Connected
updated_date: '2023-10-31T15:18:22.000Z'
org_type: dispensary
business_type: wholesale
template_id: 35fAaa1F-C959-F02f-D7E1-Dd76AAB78bA2
template_result_id: AFFef922-1F6C-CeD3-14B0-BCB94d49a5d8
status: bank_approved
mailing_street_address: 789 Main St
mailing_city: Phoenix
mailing_state: NJ
mailing_postal_code: '80202'
established_date: '2019-10-10T00:00:00.000Z'
ftEmployees: 22
ptEmployees: null
entityType: sole
dba: Green Check Dispensary
monthlySales: '20000'
monthlyCustomers: null
id: 5c88c7D3-e395-c601-625C-71Cd6DBCEB3E
name: Dispensary2
street_address: 65467 Clarence Street
street_address_2: Apt. 635
city: null
ein: 55-5555555
phone_number: (555) 555-5555
postal_code: null
country: unitedstates
state: OR
website: null
timezone: America/Los_Angeles
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/UnauthorizedError'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/ForbiddenError'
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/NotFoundError'
'422':
description: Validation Failed
content:
application/json:
schema:
$ref: '#/components/schemas/ValidateError'
description: Get all CRBs for service provider
summary: Get service provider CRBs
tags:
- Service Provider
security:
- access_auth:
- service-provider:read
- admin
parameters:
- description: Service Provider Id
in: path
name: sp_id
required: true
schema:
type: string
pattern: ^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$
post:
operationId: create-crb-for-service-provider
responses:
'200':
description: Ok
content:
application/json:
schema:
$ref: '#/components/schemas/CRB'
examples:
Example 1:
value:
mailing_street_address: 131 Main St
mailing_city: Los Angeles
mailing_state: MI
mailing_postal_code: '80202'
established_date: '2021-06-06T00:00:00.000Z'
ftEmployees: null
ptEmployees: 43
entityType: llc
dba: Green Check Dispensary
monthlySales: '20000'
monthlyCustomers: null
id: 6c1E91E6-1ffA-C89D-E2Be-7f48EeF58DCd
name: Dispensary2
street_address: 30776 Berge Mountain
street_address_2: null
city: null
ein: 55-5555555
phone_number: (555) 555-5555
postal_code: null
country: unitedstates
state: NM
website: https://genuine-parsley.name/
timezone: Pacific/Guam
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/UnauthorizedError'
examples:
Example 1:
value:
message: Unauthorized
details: We were unable to connect to [POS] using the credentials provided. Please check them and try again
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/ForbiddenError'
'404':
description: Not Found
content:
application/json:
schema:
$ref: '#/components/schemas/NotFoundError'
'409':
description: Conflict
content:
application/json:
schema:
$ref: '#/components/schemas/ConflictError'
examples:
Example 1:
value:
message: Conflict
details: The following organization(s) already exist and are connected to your account
data:
org_id: c6d67e98-83ea-49f0-8812-e4abae2b68bc
name: AlreadyConnectedDispensary
'422':
description: Validation Failed
content:
application/json:
schema:
$ref: '#/components/schemas/ValidateError'
examples:
Example 1:
value:
message: Validation Failed
details:
org.business_type:
message: Business type and point of sale type mismatch
value: wholesale
pos_info.pos_type:
message: Business type and point of sale type mismatch
value: GrowFlow
Example 2:
value:
message: Validation Failed
details:
locations:
message: Available locations
value:
- id: '1'
name: Example Dispensary
address: 420 Main St
- id: '2'
name: Example Dispensary Center Street
address: 22 Center Street
data:
locations:
- id: '1'
name: Example Dispensary
address: 420 Main St
- id: '2'
name: Example Dispensary Center Street
address: 22 Center Street
Example 3:
value:
users:
message: Users are required when POS credentials are not supplied.
value: []
pos_info.pos_credentials:
message: POS credentials are required when users are not supplied.
message: If POS credentials are not provided, users are required so that they can be invited to the app to input credentials. If users are not invited, POS credentials are required to prevent duplicate or empty organizations from being created.
description: "Create a new CRB and associate with service provider.\n\nThere are two supported onboarding workflows:\n\n1. Provide POS Credentials Up Front (`pos_info`)\n - Use when the CRB has already provided their POS credentials.\n - Include the `pos_info` object in your request.\n - Inviting users is optional.\n\n2. Invite the CRB for In-App Onboarding\n - Use when you don't have the CRB's POS credentials yet.\n - Do NOT include `pos_info`.\n - MUST include at least one user in the `users` array to send an invite.\n\nNote: You MUST provide either `pos_info` OR `users` with at least one entry. You may also provide both.\n\n-------------------------\nValidation Rules\n-------------------------\n\nIf `pos_info` is provided:\n- Org `business_type` must match `pos_type` (e.g. wholesale org must use a wholesale POS like \"Dutchie Wholesale\").\n- Credentials must be valid; a test POS call is made.\n- If the POS requires a `location_id`, it must be valid.\n - If missing or invalid, a validation error is returned with valid options.\n- The org must not already be connected to your account.\n\nIf `pos_info` is NOT provided:\n- At least one user must be included in the `users` array.\n\n-------------------------\nTesting Scenarios (Sandbox Only)\n-------------------------\n\n1. Provide `pos_info` with a wholesale POS, but `business_type = \"retail\"` → Expect validation error.\n2. Provide `pos_info` with:\n - `pos_type = \"Greenbits\"`\n - `username = \"testing\"`\n - `password = \"invalid_testing\"` → Simulates invalid credentials\n - `password = \"testing\"` → Simulates valid credentials\n3. Leave `location_id` empty → Simulates missing required location, returns available options.\n4. Set `location_id = \"invalidLocation\"` → Simulates invalid location, returns available options.\n5. Set `location_id = \"testing\"` → Simulates successful connection (no actual POS connection made)."
summary: Create CRB
tags:
- Service Provider
security:
- access_auth:
- service-provider:write
- admin
parameters:
- description: Service Provider Id
in: path
name: sp_id
required: true
schema:
type: string
pattern: ^[0-9a-fA-F]{8}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{4}\b-[0-9a-fA-F]{12}$
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/CrbCreationParams'
/service-providers/{sp_id}/pos-credentials-schema:
get:
operationId: get-service-provider-pos-credentials-schema
responses:
'200':
description: Ok
content:
application/json:
schema:
$ref: '#/components/schemas/PosCredentialInformation'
examples:
Example 1:
value:
Alleaves:
pos_type: Alleaves
business_type: retail
location_required: false
pos_credentials_schema:
credentials_name: AlleavesTestAuth
credentials_description: 'You can connect your Alleaves account to Green Check by simply using your Alleaves username and password. First, you''ll want to ensure that your user has the proper API access permissions in order for the integration to succeed. If your user has admin permissions, it should have the proper access by default.
https://support.greencheckverified.com/knowledge/connect-alleaves-to-green-check'
credentials_properties:
username:
type: string
password:
type: string
required_properties:
- password
- username
BioTrack:
pos_type: BioTrack
business_type: retail
location_required: true
pos_credentials_schema:
credentials_name: BiotrackTestAuth
credentials_description: 'BioTrack enables its users to connect to other systems like Green Check with something called a SQL to SQL Pipeline. This simply means that Green Check will have read-only access to your BioTrack data. First, you''ll need to ask BioTrack to email you the necessary credentials for the integration. Copy and paste the email below and send it to Support@biotrackthc.com. Then, you''ll need to configure BioTrack to grant Green Check access, follow the instructions found here: https://f.hubspotusercontent20.net/hubfs/5237927/Connect%20BioTrack%20to%20Green%20Check.pdf. If your Network Connection requires you to whitelist Green Check''s IP, please add these IP addresses to your whitelist: 52.4.48.232 and 35.169.209.100
Hello,
I need some assistance. I would like to integrate our system with the Green Check system. Please provide me with the necessary information about our database that the Green Check team needs for Read Only access.
https://support.greencheckverified.com/knowledge/connect-biotrack-to-green-check
https://support.greencheckverified.com/knowledge/how-to-handle-biotrack-connection-refusal-errors
https://support.greencheckverified.com/knowledge/how-to-handle-biotrack-pg_hba.conf-errors'
credentials_properties:
port:
type: number
username:
type: string
password:
type: string
server_ip:
type: string
database_name:
type: string
required_properties:
- database_name
- password
- port
- server_ip
- username
BioTrack Wholesale:
pos_type: BioTrack Wholesale
business_type: wholesale
location_required: true
pos_credentials_schema:
credentials_name: BiotrackTestAuth
credentials_description: 'BioTrack enables its users to connect to other systems like Green Check with something called a SQL to SQL Pipeline. This simply means that Green Check will have read-only access to your BioTrack data. First, you''ll need to ask BioTrack to email you the necessary credentials for the integration. Copy and paste the email below and send it to Support@biotrackthc.com. Then, you''ll need to configure BioTrack to grant Green Check access, follow the instructions found here: https://f.hubspotusercontent20.net/hubfs/5237927/Connect%20BioTrack%20to%20Green%20Check.pdf. If your Network Connection requires you to whitelist Green Check''s IP, please add these IP addresses to your whitelist: 52.4.48.232 and 35.169.209.100
Hello,
I need some assistance. I would like to integrate our system with the Green Check system. Please provide me with the necessary information about our database that the Green Check team needs for Read Only access.
https://support.greencheckverified.com/knowledge/connect-biotrack-to-green-check
https://support.greencheckverified.com/knowledge/how-to-handle-biotrack-connection-refusal-errors
https://support.greencheckverified.com/knowledge/how-to-handle-biotrack-pg_hba.conf-errors'
credentials_properties:
port:
type: number
username:
type: string
password:
type: string
server_ip:
type: string
database_name:
type: string
required_properties:
- database_name
- password
- port
- server_ip
- username
Blaze:
pos_type: Blaze
business_type: retail
location_required: false
pos_credentials_schema:
credentials_name: BlazeTestAuth
credentials_description: 'Blaze provides its users with a unique Developer Key that can be used to integrate with other systems like Green Check. In order to connect with third party applications, you will need to generate a developer key from the backend of BLAZE Retail. Follow the instructions in the link below to generate a key.
https://support.greencheckverified.com/knowledge/connect-blaze-to-green-check'
credentials_properties:
Authorization:
type: string
required_properties:
- Authorization
Canix:
pos_type: Canix
business_type: wholesale
location_required: true
pos_credentials_schema:
credentials_name: CanixTestAuth
credentials_description: 'Canix provides its users with a unique API key that can be used to integrate with other systems like Green Check. Go to your Canix settingsToggle the switch next to Green Check Verified to the on position. Copy your client API key.
https://support.greencheckverified.com/knowledge/connect-canix-to-green-check'
credentials_properties:
key:
type: string
required_properties:
- key
Dutchie:
pos_type: Dutchie
business_type: retail
location_required: false
pos_credentials_schema:
credentials_name: DutchieTestAuth
credentials_description: 'Leaf Logix/Dutchie provides its users with unique API keys that can be used to integrate with other systems like Green Check. First, you''ll need to ask Leaf Logix to email you your API credentials. Copy and paste the email below and send it to possupport@dutchie.com. Please note: If your location is licensed for both medical and recreational sales, you will have two separate API keys for this location.
Hello,
I need some assistance. I would like to integrate our system with the Green Check system. Please help me locate my API key(s) so that I can provide this to the Green Check team to set up the integration.
https://support.greencheckverified.com/knowledge/connect-leaf-logix-to-green-check'
credentials_properties:
medApiKey:
type: string
recApiKey:
type: string
required_properties: []
Dutchie Wholesale:
pos_type: Dutchie Wholesale
business_type: wholesale
location_required: false
pos_credentials_schema:
credentials_name: DutchieTestAuth
credentials_description: 'Leaf Logix/Dutchie provides its users with unique API keys that can be used to integrate with other systems like Green Check. First, you''ll need to ask Leaf Logix to email you your API credentials. Copy and paste the email below and send it to possupport@dutchie.com. Please note: If your location is licensed for both medical and recreational sales, you will have two separate API keys for this location.
Hello,
I need some assistance. I would like to integrate our system with the Green Check system. Please help me locate my API key(s) so that I can provide this to the Green Check team to set up the integration.
https://support.greencheckverified.com/knowledge/connect-leaf-logix-to-green-check'
credentials_properties:
medApiKey:
type: string
recApiKey:
type: string
required_properties: []
Flowhub:
pos_type: Flowhub
business_type: retail
location_required: true
pos_credentials_schema:
credentials_name: FlowhubTestAuth
credentials_description: 'Flowhub provides its users with a unique API key that can be used to integrate with other systems like Green Check. First, you''ll need to ask Flowhub to email you your API credentials. Please initiate the process by following this link to the Flowhub Integration Request form: https://flowhub.com/api-integration-request. Please fill out all fields and select Green Check as the desired partner and Submit.
https://support.greencheckverified.com/knowledge/connecting-flowhub-to-green-check'
credentials_properties:
key:
type: string
clientId:
type: string
required_properties:
- clientId
- key
Flourish Wholesale:
pos_type: Flourish Wholesale
business_type: wholesale
location_required: true
pos_credentials_schema:
credentials_name: FlourishTestAuth
credentials_description: 'To connect this integration, you’ll need your Flourish Username and API Key. Go to the following URL for a full guide on how to do this: https://docs.flourishsoftware.com/article/xsefgb8b0s-external-api-generate-or-reset-api-key
https://support.greencheckverified.com/knowledge/connect-flourish-to-green-check'
credentials_properties:
api_key:
type: string
required_properties:
- api_key
Greenbits:
pos_type: Greenbits
business_type: retail
location_required: true
pos_credentials_schema:
credentials_name: GreenbitsTestAuth
credentials_description: 'To share your API token with Green Check, you will need to set up a new Role and User account in Greenbits that Green Check will use to access the token. Ensure this role has the following permissions: View Products, Access Backoffice, View product types, View brands, View strains, View suppliers. Follow the instructions in the link below to set this up.
https://support.greencheckverified.com/en/knowledge/connect-greenbits-to-green-check'
credentials_properties:
username:
type: string
password:
type: string
required_properties:
- password
- username
GrowFlow:
pos_type: GrowFlow
business_type: retail
location_required: true
pos_credentials_schema:
credentials_name: GrowFlowTestAuth
credentials_description: 'First, you''ll need to ask GrowFlow to enable the Green Check integration. Log into your GrowFlow account. Using the chat bubble, ask their Support team to enable the Green Check integration for all of your locations. Then use your client ID, found in the URL of any growflow page, like: https://retail.growflow.com/c/CLIENT_ID/
https://support.greencheckverified.com/knowledge/connect-growflow-to-green-check'
credentials_properties:
client_id_name:
type: string
required_properties:
- client_id_name
GrowFlow Wholesale:
pos_type: GrowFlow Wholesale
business_type: wholesale
location_required: false
pos_credentials_schema:
credentials_name: GrowFlowWholesaleTestAuth
credentials_description: To connect this integration, you'll need your cannabis license number and the state it was issued in
credentials_properties:
state:
type: string
license_number:
type: string
required_properties:
- license_number
- state
IndicaOnline:
pos_type: IndicaOnline
business_type: retail
location_required: false
pos_credentials_schema:
credentials_name: IndicaOnlineTestAuth
credentials_description: To connect this integration, you’ll need your IndicaOnline API Key
credentials_properties:
apiKey:
type: string
officeId:
type: number
required_properties:
- apiKey
- officeId
Meadow:
pos_type: Meadow
business_type: retail
location_required: false
pos_credentials_schema:
credentials_name: MeadowTestAuth
credentials_description: 'You can connect your Meadow account to Green Check by simply using your Meadow API Key. Generate a key by navigating to your organization''s API Settings page at https://admin.getmeadow.com/settings/api. Click the "Add Integration" button. Click the Company drop-down and select "Green Check Verified". Select the "Analytics Access" checkbox.
https://support.greencheckverified.com/knowledge/connect-meadow-to-green-check'
credentials_properties:
clientKey:
type: string
required_properties:
- clientKey
POSaBIT:
pos_type: POSaBIT
business_type: retail
location_required: false
pos_credentials_schema:
credentials_name: POSaBITTestAuth
credentials_description: 'POSaBIT provides its users with a unique API Token that can be used to integrate with other systems like Green Check. Please contact POSaBIT for help in creating an api key.
https://support.greencheckverified.com/knowledge/connect-posabit-to-green-check'
credentials_properties:
apiToken:
type: string
required_properties:
- apiToken
Proteus420:
pos_type: Proteus420
business_type: retail
location_required: false
pos_credentials_schema:
credentials_name: Proteus420TestAuth
credentials_description: 'To configure this integration, you’ll need your Proteus420 Client Name and API Key. The Client Name will be the Proteus420 account name that shows on the top of the Proteus420 homepage when logged in. The API Key can be accessed and generated on the web services page (Settings>webservices). There will be a unique API Key for each location.
https://support.greencheckverified.com/knowledge/connect-proteus420-to-green-check'
credentials_properties:
clientName:
# --- truncated at 32 KB (124 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/green-check-verified/refs/heads/main/openapi/green-check-verified-service-provider-api-openapi.yml