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

LeafLink Product Subcategory API

The Product Subcategory API from LeafLink — 2 operation(s) for product subcategory.

LeafLink Product Subcategory API is one of 88 APIs that LeafLink publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Product Subcategory. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, rate-limit docs, and authentication docs.

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2022-10-31.

Requests are made against 2 base URLs: https://api.leaflink.com, https://staging-api.leaflink.com.

2 operations 2 paths 2 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2022-10-31
Base URL
https://api.leaflink.com
Authentication
HTTP Bearer, API Key
Terms of Service
Resource Areas
1

Authentication & Security 2

LeafLink Product Subcategory API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Authorization (tokenAuth). By default, every request must be authenticated.

  • bearerAuth — Authentication is done via access tokens (JWTs). See the [API authentication doc](/api/getting-started/authentication) for more information.
  • tokenAuth — Token-based authentication with required prefix "Token"

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.

Product Subcategory 2
GET
/product_subcategories
List Product Subcategories
product_subcategories_list 8 params → 200429
GET
/product_subcategories/{id}
Get a Product Subcategory
product_subcategories_retrieve 2 params → 200429

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are UnifiedProductSubCategory (4 properties), PaginatedUnifiedProductSubCategoryList (4 properties). Each schema is shown below with its type and property counts.

PaginatedUnifiedProductSubCategoryList
object
4 properties 2 required
UnifiedProductSubCategory
object
Unified Product Subcategory serializer
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leaflink-product-subcategory-api-openapi.yml Raw ↑

Other APIs LeafLink publishes across the network.

LeafLink Active Entry API
LeafLink Activity Entries API
LeafLink Batch API
LeafLink Batch Documents API
LeafLink Batches API
LeafLink Brand API
LeafLink Brands API
LeafLink Buyer Orders API
LeafLink Buyer Product Image API
LeafLink Chats API
LeafLink Companies API
LeafLink Company API
Where this information came from

This is an independent, third-party profile of LeafLink Product Subcategory 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.