How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
LeafLink

LeafLink Marketplace V2 API

The legacy LeafLink Marketplace V2 REST API, currently at release 2.39.0. 66 paths and 111 operations for brands and retailers: orders received, buyer orders, line items, order payments and event logs, products and product batches, customers, customer statuses and tiers, credits, licenses, retailer inventory, strains, reports and promo codes. Token/App-key auth, limit/offset paging, dynamic responses via include_children and fields_include/fields_exclude.

Documentation Provider Profile APIs.io OpenAPI GitHub

LeafLink Marketplace V2 API is one of 2 APIs that LeafLink publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Cannabis, Wholesale, Order, Product, and Customers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, and a changelog.

This API exposes 111 operations across 66 paths, organized into 32 resource areas, and defines 74 schemas. It is described by OpenAPI 3.0.0.

Requests are made against a single base URL, https://app.leaflink.com/api/v2.

111 operations 66 paths 74 schemas 14 DELETE65 GET12 PATCH20 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
Base URL
https://app.leaflink.com/api/v2
Authentication
API Key
Contact
support@leaflink.com
Terms of Service
View terms
Resource Areas
32

Authentication & Security 1

LeafLink Marketplace V2 API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Token). By default, every request must be authenticated.

  • Token — You must authenticate your requests by including your API key in each request header as described below. Requests should include a header named Authorization,…

Paths & Operations 111

Across 66 paths, the API surfaces 111 operations — 14 DELETE, 65 GET, 12 PATCH, 20 POST. They span 32 resource areas, including activity-entries, batch-documents, batches, inventory-items, facilities, brands, companies, company-staff, and 24 more. Each is listed below with its method, path, parameters, and response codes.

activity-entries 5

The CompanyActivityEntry model represents a CRM action taken by a staff member that relates to a customer, with an optional description.

GET
/activity-entries/
List
activity-entries_list 41 params → 200
POST
/activity-entries/
Create
activity-entries_create body → 201
GET
/activity-entries/{id}/
Read
activity-entries_read 1 param → 200
PATCH
/activity-entries/{id}/
Update
activity-entries_partial_update 1 param body → 200
DELETE
/activity-entries/{id}/
Delete
activity-entries_delete 1 param → 200
batch-documents 4
GET
/batch-documents/
List batch documents
→ 200
POST
/batch-documents/
Upload a batch document
body → 201
GET
/batch-documents/{id}/
Retrieve a batch document
batch-documents_read 1 param → 200
DELETE
/batch-documents/{id}/
Delete a batch document
batch-documents_delete 1 param → 204
batches 5
GET
/batches/
List batches
batches_list 19 params → 200
POST
/batches/
Create a batch
batches_create body → 201
GET
/batches/{id}/
Retrieve a batch
batches__read 1 param → 200
PATCH
/batches/{id}/
Update a batch
batches__partial_update 1 param body → 200
DELETE
/batches/{id}/
Delete a batch
batches__delete 1 param → 204
inventory-items 4

The InventoryItem model represents items of a particular inventory batch at a given facility.

GET
/inventory/items/
List
inventory-items_list 2 params → 200
POST
/inventory/items/
Create
inventory-items_create body → 201
GET
/inventory/items/{id}/
Read
inventory-items_read 2 params → 200
PATCH
/inventory/items/{id}/
Update
inventory-items_partial_update 2 params body → 200
facilities 2

The Facility model represents a location where inventory is located.

GET
/inventory/facilities/
List
facilities_list → 200
GET
/inventory/facilities/{id}/
Read
facilities_read 1 param → 200
brands 2
GET
/brands/
List brands
brands_list 5 params → 200
GET
/brands/{id}/
Retrieve a brand
brands_read 1 param → 200
companies 2
GET
/companies/
List companies
companies_list 2 params → 200
GET
/companies/{id}/
Retrieve a company
companies_read 1 param → 200
company-staff 2
GET
/company-staff/
List staff members
company-staff_list 6 params → 200
GET
/company-staff/{id}/
Retrieve a staff member
company-staff_read 1 param → 200
contacts 5

The Contact model represents the contact information a user has stored as a company resource within LeafLink.

GET
/contacts/
List
contacts_list 20 params → 200
POST
/contacts/
Create
contacts_create body → 201
GET
/contacts/{id}/
Read
contacts_read 1 param → 200
PATCH
/contacts/{id}/
Update
contacts_partial_update 1 param body → 200
DELETE
/contacts/{id}/
Delete
contacts_delete 1 param → 204
customer-statuses 5

The CompanyCustomerStatus represents a set of customizable states for customers in the sales funnel.

GET
/customer-statuses/
List
customer-statuses_list 15 params → 200
POST
/customer-statuses/
Create
customer-statuses_create body → 201
GET
/customer-statuses/{id}/
Read
customer-statuses__read 1 param → 200
PATCH
/customer-statuses/{id}/
Update
customer-statuses_partial_update 1 param body → 200
DELETE
/customer-statuses/{id}/
Delete
customer-statuses_delete 1 param → 204
customer-tiers 2

The CompanyCustomerTier represents a set of read only objects depicting a customer's tier in relationship to a company.

GET
/customer-tiers/
List
customer-tiers_list 2 params → 200
GET
/customer-tiers/{id}/
Read
customer-tiers__read 1 param → 200
credits 2

The Credit model represents credits granted by a seller company to a customer for use in future purchases. Read-only.

GET
/credits/
List
credits_list 14 params → 200
GET
/credits/{id}/
Read
credits_read 1 param → 200
customers 5

The Customer model represents a business relationship between a buyer and seller on LeafLink.

GET
/customers/
List customers
customers_list 88 params → 200
POST
/customers/
Create a customer
customers_create body → 201
GET
/customers/{id}/
Retrieve a customer
customers_read 4 params → 200
PATCH
/customers/{id}/
Update a customer
customers_partial_update 1 param body → 200
DELETE
/customers/{id}/
Archive a customer
customers_delete 1 param → 200
license-types 2

The LicenseType model represents a category of state-issued licenses.

GET
/license-types/
List
license-types_list 2 params → 200
GET
/license-types/{id}/
Read
license-types_read 1 param → 200
licenses 2

The License model represents a single state-issued license held by a Company.

GET
/licenses/
List
licenses_list 6 params → 200
GET
/licenses/{id}/
Read
licenses_read 1 param → 200
line-items 6

The LineItem model represents a single entry in an itemized purchase order.

GET
/line-items/
List line items
line-items_list 19 params → 200
POST
/line-items/
Create line item
line-items_create body → 201
GET
/line-items/{id}/
Retrieve a line item
line-items_read 2 params → 200
PATCH
/line-items/{id}/
Update a line item
line-items_partial_update 1 param body → 200
DELETE
/line-items/{id}/
Delete a line item
line-items_delete 1 param → 204
GET
/orders-received/{number}/line-items/
List line items
orders-received-line-items_list 1 param → 200
order-event-logs 2
GET
/order-event-logs/
List
order-event-logs_list 5 params → 200
GET
/order-event-logs/{id}/
Read
order-event-logs_read 1 param → 200
order-payments 4
GET
/order-payments/
List payments
order-payments_list 2 params → 200
POST
/order-payments/
Create a payment
order-payments_create body → 201
GET
/order-payments/{id}/
Retrieve a payment
order-payments_read 1 param → 200
GET
/orders-received/{number}/payments/
List payments
orders-received-payments_list 1 param → 200
order-sales-reps 4
GET
/order-sales-reps/
List
order-sales-reps_list 2 params → 200
POST
/order-sales-reps/
Create
order-sales-reps_create body → 201
GET
/order-sales-reps/{id}/
Read
order-sales-reps_read 1 param → 200
DELETE
/order-sales-reps/{id}/
Delete
order-sales-reps_delete 1 param → 204
buyer-orders 1
GET
/buyer/orders/
List orders
buyer-orders_list 33 params → 200
orders-received 7

Access the order object

GET
/orders-received/
List orders
orders-received_list 35 params → 200
POST
/orders-received/
Create an order
orders-received_create body → 201
GET
/orders-received/{number}/
Retrieve an order
orders-received_read 5 params → 200
PATCH
/orders-received/{number}/
Update an order
orders-received_partial_update 1 param body → 200
DELETE
/orders-received/{number}/
Delete a draft order
orders-received_delete 1 param → 204
POST
/orders-received/{number}/transition/{action}/
Transition an order
orders-received_transition_create 2 params → 200
GET
/orders/{order_number}/delivery-information/
Retrieve delivery information
orders-received-delivery-information_read 1 param → 200
order-comments 1
GET
/orders-received/{number}/comments/
List comments
orders-received-comments_list 1 param → 200
product-batches 4

Manage assignments.

GET
/product-batches/
List assignments
product-batches_list 2 params → 200
POST
/product-batches/
Create an assignment
product-batches_create body → 201
GET
/product-batches/{id}/
Retrieve an assignment
product-batches__read 1 param → 200
DELETE
/product-batches/{id}/
Delete an assignment
product-batches__delete 1 param → 204
product-categories 2
GET
/product-categories/
List categories
product-categories_list 2 params → 200
GET
/product-categories/{id}/
Retrieve a category
product-categories_read 1 param → 200
product-images 4

Product images for display in the marketplace. Each product may have up to 5 images.

GET
/product-images/
List images
product-images_list 5 params → 200
POST
/product-images/
Upload an image
product-images_create body → 201
GET
/product-images/{id}/
Retrieve an image
product-images_read 1 param → 200
DELETE
/product-images/{id}/
Delete an image
product-images_delete 1 param → 204
product-lines 4
GET
/product-lines/
List product lines
product-lines_list 6 params → 200
POST
/product-lines/
Create a product line
product-lines_create body → 201
GET
/product-lines/{id}/
Retrieve a product line
product-lines_read 1 param → 200
PATCH
/product-lines/{id}/
Update a product line
product-lines_partial_update 1 param body → 200
product-subcategories 2
GET
/product-subcategories/
List subcategories
product-subcategories_list 2 params → 200
GET
/product-subcategories/{id}/
Retrieve a subcategory
product-subcategories_read 1 param → 200
products 5

The Product model represents a physical product offered for sale by a Company.

GET
/products/
List products
products_list 43 params → 200
POST
/products/
Create a product
products_create body → 201
GET
/products/{id}/
Retrieve a product
products_read 4 params → 200
PATCH
/products/{id}/
Update a product
products_partial_update 1 param body → 200
DELETE
/products/{id}/
Archive a product
products_delete 1 param → 200
promocodes 5

The Promocode model represents a promotional discount code for a specific Brand.

GET
/promocodes/
List
promocodes_list 5 params → 200
POST
/promocodes/
Create
promocodes_create body → 201
GET
/promocodes/{id}/
Read
promocodes__read 1 param → 200
PATCH
/promocodes/{id}/
Update
promocodes__partial_update 1 param body → 200
DELETE
/promocodes/{id}/
Delete
promocodes__delete 1 param → 204
reports 3

The Report model represents a report download initiated by a User

GET
/reports/
List
reports_list 3 params → 200
POST
/reports/
Create
reports_create body → 201
GET
/reports/{number}/
Read
reports__read 1 param → 200
strains 3
GET
/strains/
List strains
strains_list 9 params → 200
POST
/strains/
Create a strain
strains_create body → 201
GET
/strains/{id}/
Retrieve a strain
strains_read → 200
retailer-inventory 5

Product information for a retailer company.

GET
/retailer-inventory/
List products
retailer-inventory_list 3 params → 200
POST
/retailer-inventory/
Create a product
retailer-inventory_create body → 201
GET
/retailer-inventory/{id}/
Retrieve a product
retailer-inventory_read 1 param → 200
PATCH
/retailer-inventory/{id}/
Update a product
retailer-inventory_partial_update 1 param body → 200
DELETE
/retailer-inventory/{id}/
Delete a product
retailer-inventory_delete 1 param → 204

Schemas 74

The contract defines 74 schemas that model the data the API accepts and returns. The most detailed are ProductResponse (62 properties), ProductArchiveResponse (61 properties), ProductUpdateResponse (61 properties), CustomerResponse (54 properties). Each schema is shown below with its type and property counts.

RetailerInventory
object
11 properties 8 required
RetailerInventoryResponse
object
11 properties
RetailerInventoryCreate
object
8 properties 8 required
RetailerInventoryUpdate
object
8 properties
CompanyActivityEntry
object
14 properties 4 required
BatchDocumentNew
object
6 properties
BatchCreate
object
13 properties 4 required
BatchUpdate
object
11 properties
BatchResponse
object
16 properties
InventoryItemCreate
object
5 properties 5 required
InventoryItemUpdate
object
2 properties
InventoryItem
object
10 properties
Facility
object
3 properties
LightCompanyCustomer
object
Seller's customer record for the company on the buyer side of the order
4 properties 2 required
LightCompanyCustomerId
object
Seller's customer record for the company on the buyer side of the order
1 property 1 required
LineItem
object
23 properties 3 required
LineItemCreate
object
17 properties 4 required
LineItemResponse
object
23 properties
LineItemUpdate
object
10 properties
LightCompanyStaffId
object
Sales representatives associated with the order.
1 property
LightCompanyStaff
object
Sales representatives associated with the order.
2 properties
LightOrderTax
object
Details about the taxes applied to the order
7 properties 2 required
BrandOwnerOrderInternal
object
35 properties 3 required
BrandResponse
object
6 properties
ProductImageResponse
object
Images for the product
4 properties
UnitDenomination
object
4 properties 3 required
CompanyResponse
object
21 properties
CompanyReportSchedule
object
3 properties 2 required
ReportDownload
object
10 properties 2 required
CompanyStaffResponse
object
11 properties
Contact
object
15 properties 2 required
CompanyCustomerContact
object
6 properties 2 required
CompanyCustomerStatus
object
7 properties 2 required
CompanyCustomerTag
object
3 properties 2 required
CompanyCustomerTier
object
5 properties 2 required
Credit
object
Credit granted by a seller company to a customer for use in future purchases. Read-only.
17 properties
CustomerCreate
object
49 properties 2 required
CustomerUpdate
object
48 properties
CustomerResponse
object
54 properties
DeliveryProviderOrderInformation
object
4 properties
LicenseType
object
14 properties 4 required
ComplianceLicense
object
5 properties 1 required
OrderComment
object
7 properties 3 required
OrderEventLog
object
12 properties 1 required
OrderPaymentCreate
object
6 properties 4 required
OrderPaymentResponse
object
10 properties
OrderDeliveryInformation
object
Order delivery information payload.
OrderSalesRepSerialzer
object
4 properties 2 required
ProductBatchResponse
object
3 properties
ProductBatchCreate
object
2 properties 2 required
ProductCategoryResponse
object
4 properties
ProductLineResponse
object
4 properties
ProductLineCreate
object
3 properties 2 required
ProductLineUpdate
object
3 properties
ParentProduct
object
Parent product to which this product belongs. Required if creating a variety (child product) of a parent product. Varieties are useful when selling a single pr…
1 property 1 required
ProductCreate
object
44 properties 19 required
ProductUpdate
object
45 properties
ProductUpdateResponse
object
61 properties
ProductArchiveResponse
object
61 properties
ProductResponse
object
62 properties
PromoCode
object
7 properties 4 required
StrainResponse
object
5 properties
StrainCreate
object
4 properties 2 required
StrainUpdate
object
4 properties
Order
object
44 properties 3 required
OrderResponse
object
52 properties
ExternalIds
object
Set of key-value pairs for storing external system IDs. Key value can be up to 36 characters long.
Address
object
6 properties
OrderAddress
object
Read only delivery address as provided during order creation.
5 properties
OrderUpdate
object
26 properties
OrderCreate
object
25 properties 4 required
BuyerLicense
object
4 properties
BuyerOrderResponse
object
28 properties
ProductSubcategoryResponse
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leaflink-marketplace-v2-openapi-original.yml Raw ↑

Other APIs LeafLink publishes across the network.

LeafLink API
AE Profile APIs.io
#Cannabis#Wholesale#Order#Product#Customers#Legacy
← Back to L APIs
API Details
ID
leaflink:marketplace-v2
Base URL
https://app.leaflink.com/api/v2
Docs
https://developer.leaflink.com/legacy/v2/api/getting-started/
Provider
LeafLink
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=marketplace-v2&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/marketplace-v2"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of LeafLink Marketplace V2 API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.