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 Customers API

The customers API from LeafLink — 7 operation(s) for customers.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Customers. 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 16 operations across 7 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

16 operations 7 paths 20 schemas 5 DELETE2 GET4 PATCH4 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.leaflink.com
Authentication
HTTP Bearer, API Key, API Key
Contact
support@leaflink.com
Resource Areas
1

Authentication & Security 3

LeafLink Customers API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Authorization (tokenAuth). An API key is passed in the header as Authorization (Token).

  • 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"
  • 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 16

Across 7 paths, the API surfaces 16 operations — 5 DELETE, 2 GET, 4 PATCH, 4 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

customers 16
POST
/customers
LeafLink API for Marketplace customers.
customers_create body → 201429
PUT
/customers/{id}
LeafLink API for Marketplace customers.
customers_update 2 params body → 200429
PATCH
/customers/{id}
LeafLink API for Marketplace customers.
customers_partial_update 2 params body → 200429
DELETE
/customers/{id}
For delete request
customers_destroy 2 params → 204429
POST
/customers/{id}/corporate_address
Action route for interfacing with the corporate address
customers_corporate_address_create 2 params body → 200429
PATCH
/customers/{id}/corporate_address
Action route for interfacing with the corporate address
customers_corporate_address_partial_update 2 params body → 200429
DELETE
/customers/{id}/corporate_address
Action route for interfacing with the corporate address
customers_corporate_address_destroy 2 params → 204429
POST
/customers/{id}/delivery_address
Action route for interfacing with the delivery address
customers_delivery_address_create 2 params body → 200429
PATCH
/customers/{id}/delivery_address
Action route for interfacing with the delivery address
customers_delivery_address_partial_update 2 params body → 200429
DELETE
/customers/{id}/delivery_address
Action route for interfacing with the delivery address
customers_delivery_address_destroy 2 params → 204429
DELETE
/customers/active_entries/{id}
Delete an Active Entry for a company
customers_active_entries_destroy 2 params → 204429
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

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are CustomerResponse (54 properties), CustomerCreate (49 properties), CustomerUpdate (48 properties), UnifiedCustomer (41 properties). Each schema is shown below with its type and property counts.

TierEnum
integer
PaymentProgramEnum
string
UnifiedCompanyCustomerStatus
object
Unified serializer for the CompanyCustomerStatus model.
7 properties 2 required
ShortPaymentMethod
object
Short serializer for payment methods.
2 properties 2 required
PatchedUnifiedAddressRequest
object
Inherits AddressSerializer but sets the FK relation on the resource Model
6 properties
ServiceZone
object
Serializer for the ServiceZone model.
4 properties 3 required
NullEnum-unified-upstream-marketplace
UnifiedAddress
object
Inherits AddressSerializer but sets the FK relation on the resource Model
6 properties 4 required
CustomerPaymentOptionSerializerV2
object
External serializer class for Customers payment options.
6 properties
PaymentStrategyEnum
string
ShortPaymentTerm
object
Short serializer for payment terms.
4 properties 3 required
PatchedUnifiedCustomerRequest
object
UnifiedCustomerSerializer inherits existing v2 CompanyCustomerSerializer for validations
28 properties
UnifiedAddressRequest
object
Inherits AddressSerializer but sets the FK relation on the resource Model
6 properties 4 required
UnifiedCustomerRequest
object
UnifiedCustomerSerializer inherits existing v2 CompanyCustomerSerializer for validations
28 properties 2 required
UnifiedCustomer
object
UnifiedCustomerSerializer inherits existing v2 CompanyCustomerSerializer for validations
41 properties 17 required
CustomerResponse
object
54 properties
Address
object
6 properties
ExternalIds
object
Set of key-value pairs for storing external system IDs. Key value can be up to 36 characters long.
CustomerUpdate
object
48 properties
CustomerCreate
object
49 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leaflink-customers-api-openapi.yml Raw ↑

Other APIs LeafLink publishes across the network.

LeafLink Active Entry API
AE Profile APIs.io
LeafLink Activity Entries API
AE Profile APIs.io
LeafLink Batch API
AE Profile APIs.io
LeafLink Batch Documents API
AE Profile APIs.io
LeafLink Batches API
AE Profile APIs.io
LeafLink Brand API
AE Profile APIs.io
LeafLink Brands API
AE Profile APIs.io
LeafLink Buyer Orders API
AE Profile APIs.io
LeafLink Buyer Product Image API
AE Profile APIs.io
LeafLink Chats API
AE Profile APIs.io
LeafLink Companies API
AE Profile APIs.io
LeafLink Company API
AE Profile APIs.io
#Customers
← Back to L APIs
API Details
ID
leaflink:leaflink-customers-api
Base URL
https://api.leaflink.com
Docs
https://developer.leaflink.com/api/
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=leaflink-customers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/leaflink-customers-api"

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 Customers 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.