canonical: https://jentic.com/apis/www.leaflink.com/leaflink

# LeafLink Marketplace V2 API

Introduction HTTP Request Notes All endpoints covered in this document are preceded by `https://{{domain}}/api/v2/` unless otherwise noted. Available domains - `www.leaflink.com` - production environment - `sandbox.leaflink.com` - sandbox environment - `leaflink-integrations.leaflink.com` -. The API exposes 105 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create, list. Covers 105 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create
- List
- Read
- Update
- Delete
- Upload a batch document

## Use cases

### E-Commerce Operations

Use the LeafLink Marketplace V2 API to perform e commerce operations programmatically. The API provides 105 endpoints covering core functionality including create, list, read.

Example prompt: Call POST /activity-entries to create

### Automated orders-received Management

Automate orders-received operations by combining multiple LeafLink Marketplace V2 API endpoints. Agents can list and then read in a single workflow.

Example prompt: Call GET /activity-entries to list, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call LeafLink Marketplace V2 API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'create', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/activity-entries` | Create |
| GET | `/activity-entries` | List |
| GET | `/activity-entries/{id}` | Read |
| PATCH | `/activity-entries/{id}` | Update |
| DELETE | `/activity-entries/{id}` | Delete |
| POST | `/batch-documents` | Upload a batch document |
| GET | `/batch-documents` | List batch documents |
| GET | `/batch-documents/{id}` | Retrieve a batch document |

## Key resources

- **orders-received** — Access the order object
- **activity-entries** — The `CompanyActivityEntry` model represents a CRM action taken by a staff member that relates to a c
- **customers** — The Customer model represents a business relationship between a buyer and seller on LeafLink.
- **customer-statuses** — The `CompanyCustomerStatus` represents a set of customizable states for customers in the sales funne
- **line-items** — The LineItem model represents a single entry in an itemized purchase order.

## Why Jentic

- **Setup:** Wiring the LeafLink Marketplace V2 API by hand means sending its Token header and managing marketplace resources across 105 operations yourself. Through Jentic you install once, import the LeafLink Marketplace V2 API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The LeafLink Marketplace V2 API puts the resource id in the URL path (`/activity-entries/{id}`, `/batch-documents/{id}`), so a rule can pin your agent to one activity entry or batch document. You choose the operations it may call, so destructive ones like deleting an activity entry are not included unless you add them.
- **Credential handling:** Your LeafLink Marketplace V2 API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an activity entry' or 'list batch documents', and Jentic returns the matching LeafLink Marketplace V2 API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the LeafLink Marketplace V2 API use?

The LeafLink Marketplace V2 API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create with the LeafLink Marketplace V2 API?

Yes. Use the POST /activity-entries endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the LeafLink Marketplace V2 API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create'. Jentic returns the matching LeafLink Marketplace V2 API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the LeafLink Marketplace V2 API have?

The LeafLink Marketplace V2 API exposes 105 endpoints covering orders-received, activity-entries, customers operations.

### Can I limit what my agent is allowed to do with the LeafLink Marketplace V2 API?

Yes. Jentic One is self-hosted by you, so your own rules decide which LeafLink operations and credentials the agent may use. Because the API puts the resource id in the URL path, such as `/activity-entries/{id}` and `/batch-documents/{id}`, a rule can pin the agent to a single activity entry or batch document. You pick the operations it can call, so destructive actions like DELETE `/activity-entries/{id}` stay off limits unless you add them.