We offer you various APIs. If you have a Channel Pilot Pro customer account, you can use them free of charge.
Product API
The Product API connects your product database, shop system, or ERP directly to Channel Pilot Pro — without any additional intermediate processes.
Channel Pilot Pro offers its own "REST-API" for importing your product data.
This "Product API" provides basic functions such as creating, updating, and deleting product data. It can be integrated into your existing import process - just like a regular import - or even fully replace it.
Unlike other import methods, your shop system or your ERP system pushes to Channel Pilot Pro via the "Product API" rather than being retrieved by Channel Pilot Pro. This allows you to determine more precisely when specific data should be imported.
The API stores data incrementally, allowing updates to be processed even when full product feed files are in use.
This enables key use cases, such as improved performance and scalability for large catalogs, fast stock and price updates, and streamlined system‑to‑system integrations (ERP/PIM/WMS) without the need for file generation or transfer.
You can find the latest version of the full Product API documentation here.
To authenticate, you need the apiMerchantId and apiToken, which you can find in the shop settings.
All data transfers via the Product API are tailored to each shop and feed.
If you want to update data across multiple feeds or shops, simply send a dedicated request for each feed with the generated token of the related shop.
Basics of Product API
Just as Channel Pilot Pro offers you a REST-API for automated control of your marketing activities, it is also possible to connect any import via "Product API".
Contrary to other import variants, the data is pushed from your side via API to Channel Pilot Pro and not retrieved by Channel Pilot Pro.
The following functions are available within the "Product API":
POST AUTHENTIFICATION -> Identification of the connection and generation of a token
Manipulation of product data
PUT / PUT_OR_CREATE (New Data -> Update)
PATCH / PATCH_OR_CREATE (Additional Data -> Replace)
DELETE
GET SETUP FOR FEEDS -> Information about the setup
Import via Product API
On "Import source" click "Product API".
Next you have to enter the "Unique article identifier", which will be used as SKU.
It does not have to be named "SKU" in your import source.
Click "Next".
Click "Save all".
It directly shows you the link to our official "Swagger Documentation" for "Product-API"
POST Authentication - Creation of a "Bearer Token"
POST /authentication/login
Use this request with the correct apiMerchantId and apiToken as json-body to acquire an authentication-token valid for one hour. The token is needed for all other requests.
Those information are available in the shop settings:
Request:
{
"apiMerchantId": "string",
"apiToken": "string"
}
Response:
{
"access_token": "demotoken"
"token_type": "Bearer"
"expires_in": "3600"
}
How Offsets Work in API Calls
Each feed you connect to has its own independent offset sequence. The offset starts at 0 and increases by 1 every time a product update is added to that specific feed. When you make an API request, you can use the offset to control which updates you retrieve.
A simple way to check how far your processing has progressed is to look at the endOffset value returned in your most recent request. If the last offset shown in the response has already been processed on your side, it means that all earlier updates have also been completed. This makes offsets a reliable way to track incremental updates and ensure nothing is missed.