BaseLinker API

Name: BaseLinker API API
Brand: BaseLinker API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder ManagementapiKey1 EndpointsREST

For Agents

Manage marketplace orders, inventory, products, and shipping labels in BaseLinker through its single-endpoint method dispatch API. Useful for agents automating multi-channel e-commerce operations.

Quickstart

Get started with BaseLinker API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list new baselinker orders"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BaseLinker API API.

Pull orders from connected marketplaces and online stores into BaseLinker

Update inventory levels across products and warehouses

Create and edit products with prices, attributes, and stock counts

Generate shipping labels and track parcels with connected couriers

Trigger custom BaseLinker order statuses to drive operational workflows

GET STARTED

Start building with BaseLinker API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for BaseLinker API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for the BaseLinker API, keeping it validated and agent-ready. BaseLinker is an e-commerce operations platform that connects marketplaces, online stores, warehouses, and shipping carriers under a single backend. The API exposes a single connector endpoint at /connector.php where the requested method name and JSON parameters are submitted in the POST body, covering order management, inventory, product catalogues, and shipping label generation. Used by merchants automating multi-channel order processing across marketplaces such as Allegro, Amazon, eBay, and Shopify.

Use Cases

Patterns agents use BaseLinker API API for, with concrete tasks.

★ Multi-Channel Order Aggregation

Pull orders from connected marketplaces and online stores into a single BaseLinker queue and process them through one workflow. Calls to /connector.php with order-related methods like getOrders or getJournalList retrieve orders, while status update methods drive picking, packing, and dispatch. This replaces logging into each marketplace separately and centralises order operations.

POST /connector.php with method=getOrders and date_from set to today's start to retrieve all new orders, then iterate the response and apply local processing rules.

Inventory Sync Across Warehouses and Channels

Keep stock levels consistent across BaseLinker, ERPs, and marketplaces by pushing updates through inventory methods on /connector.php. Methods like updateInventoryProductsStock take product IDs and per-warehouse stock counts in a single payload, so a single call can synchronise dozens of SKUs. Useful for high-volume retailers that listed in multiple marketplaces and risk overselling.

POST /connector.php with method=updateInventoryProductsStock and a products payload that decrements stock by the quantities sold in the last hour on each marketplace.

Automated Shipping Label and Status Updates

Generate shipping labels for paid orders and advance the order through fulfilment statuses without operator clicks. The shipping methods on /connector.php integrate with connected courier accounts to produce labels and tracking numbers, while status methods write the operational state back into BaseLinker. This is a typical hand-off between WMS and BaseLinker for parcel-heavy merchants.

POST /connector.php with method=createPackage for an order ID and connected courier, then POST again with method=setOrderStatus to advance the order to 'shipped'.

AI Agent Order Operations Assistant via Jentic

Run an AI agent that answers operational questions like 'how many orders shipped today' or 'what's stock on SKU 123 across warehouses' by calling BaseLinker through Jentic. The agent searches Jentic for an intent like 'list new baselinker orders' or 'check baselinker stock', loads the matched method dispatch payload, and executes the call with the X-API-Key header held in the Jentic vault.

Search Jentic for 'list new baselinker orders', execute /connector.php with method=getOrders for the current date, and respond with a count grouped by marketplace.

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for the baselinker api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/connector.php

Execute any BaseLinker method by passing method name and parameters in the request body

POST

/connector.php

Execute any BaseLinker method by passing method name and parameters in the request body

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BaseLinker API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution access, and the X-API-Key header is injected at request time so the raw key never enters the LLM context window.

Intent-based discovery

Agents search by intent (for example, 'list new baselinker orders' or 'update product stock') and Jentic returns the matched method dispatch operation with its input schema, mapping cleanly onto BaseLinker's single connector endpoint.

Time to first call

Direct BaseLinker integration: 1-2 days to map the dispatch model and per-method payloads. Through Jentic: under 1 hour, since Jentic abstracts the connector endpoint into discrete operations the agent can call by name.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ShipStation

Multi-carrier shipping and order management focused on US carriers.

Pick ShipStation when US carrier integrations dominate; pick BaseLinker when European marketplaces (especially Allegro) and broader inventory operations are the focus.

Complementary

Stripe

Payment processing platform that pairs with BaseLinker for end-to-end checkout.

Use Stripe for payment capture and BaseLinker for downstream order, inventory, and shipping operations.

Complementary

Asana

Task management for operations teams running BaseLinker workflows.

Use Asana for human task tracking and BaseLinker for the automated marketplace and shipping operations themselves.

FAQs

Specific to using BaseLinker API API through Jentic.

Why is there no official OpenAPI spec for BaseLinker?

BaseLinker does not publish an OpenAPI specification, only narrative method-by-method documentation. Jentic generates and maintains this spec so that AI agents and developers can call BaseLinker via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the BaseLinker API use?

BaseLinker uses an API key sent in the X-API-Key request header. There is a single connector endpoint and the method to invoke is passed in the body. When called through Jentic, the API key is held encrypted in the Jentic vault and injected at execution time, so the agent's context never sees the raw key.

How does BaseLinker's single-endpoint method dispatch work?

All BaseLinker calls go to POST /connector.php. The body contains a method field naming the operation (for example, getOrders) and a parameters field with method-specific JSON. The same endpoint and auth header are reused for every operation, which means that the OpenAPI spec describes a single path but Jentic exposes each method as a discoverable operation with its own input schema.

Can I sync orders from marketplaces into BaseLinker?

Yes. Use methods like getOrders or getJournalList on /connector.php to pull aggregated marketplace orders into BaseLinker. Status update methods then drive picking, packing, and dispatch back into the source channels.

What are the rate limits for the BaseLinker API?

BaseLinker enforces account-scoped rate limits expressed as requests per minute and per day; the exact numbers depend on plan and historical usage. For bulk operations, prefer batch methods (for example, updateInventoryProductsStock with multiple products in one payload) over per-record loops.

How do I generate a shipping label through Jentic?

Install the Jentic SDK with pip install jentic, search for 'create a baselinker shipping label', and execute /connector.php with method=createPackage and the courier and order parameters. Jentic injects the X-API-Key header and returns the tracking number from BaseLinker for the agent to record.