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

The contacts API from LeafLink — 4 operation(s) for contacts.

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

Tagged areas include Contacts. 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 9 operations across 4 paths, and defines 4 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.

9 operations 4 paths 4 schemas 2 DELETE2 GET2 PATCH2 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
Resource Areas
1

Authentication & Security 3

LeafLink Contacts 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 9

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

contacts 9
POST
/contacts
LeafLink API for Marketplace contacts.
contacts_create body → 201429
PUT
/contacts/{id}
LeafLink API for Marketplace contacts.
contacts_update 2 params body → 200429
PATCH
/contacts/{id}
LeafLink API for Marketplace contacts.
contacts_partial_update 2 params body → 200429
DELETE
/contacts/{id}
Perform a 'DELETE' on a contact. It will mark the specified contact as Deleted.
contacts_destroy 2 params → 204429
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

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Contact (15 properties), UnifiedContact (15 properties), PatchedUnifiedContactRequest (12 properties), UnifiedContactRequest (12 properties). Each schema is shown below with its type and property counts.

UnifiedContactRequest
object
Unified Contact serializer
12 properties 2 required
UnifiedContact
object
Unified Contact serializer
15 properties 5 required
PatchedUnifiedContactRequest
object
Unified Contact serializer
12 properties
Contact
object
15 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leaflink-contacts-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 Contacts 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.