Who this page is for
This one assumes you are writing code. If you only want an AI assistant to read and act on your EasyChannel data, the MCP route is quicker and needs no programming: see: How to connect AI agents to EasyChannel using MCP. Both run on the same platform and accept the same credentials.
Base URL and versioning
Everything is served from:
https://api.easychannel.com
Resource endpoints sit under /v1/. A products call, in full:
GET https://api.easychannel.com/v1/products
JSON in, JSON out, over HTTPS. Authentication and health endpoints sit outside the version prefix.
Two ways to authenticate
Both resolve to the same thing: a bearer token attached to your EasyChannel company.
Token from the app. The fastest path for scripts and internal tools you own. Take it from Settings > Integrations > API EasyChannel (the MCP tile issues an equivalent token for the same account) and attach it to every request:
Authorization: Bearer YOUR_TOKEN_HERE
Regenerating the token from that dialog kills the previous one on the spot, which is your emergency switch if it ever gets out.
OAuth 2.0, authorization code flow. The right choice when your software acts for sellers other than yourself, since nobody has to hand you a raw token.
Send the seller to
GET /auth/authorizeExchange the code you get back at
POST /auth/tokenUse the returned access token in the same
AuthorizationheaderCall
GET /auth/meany time you need to confirm a token is still live
Either way, the credential resolves to one company. Calls that concern a single marketplace account need that account's seller ID, which GET /v1/sellers returns.
Endpoint reference
The complete list of paths, parameters, and response shapes lives at:
That page is generated from the live API, so it cannot drift out of date. Take it as the authority over anything written here. Broadly it covers:
Products with variants, identifiers, custom attributes, categories, tags, and SKU templates
Listings, the channel-level view of each product, with tags
Mapping templates, including bulk application of channel field mappings
Orders per seller account, with tags
Sellers and their marketplace business policies
Segments, your saved filter sets, usable to scope other queries
CSV imports with row-level error detail
Bulk actions, queued from a catalog of operations and polled for progress
Webhooks
Rather than polling, register an endpoint of yours and let EasyChannel call it.
POST /webhooks/subscribe POST /webhooks/unsubscribe
The current event list and payload shapes are in the API documentation. Points worth knowing:
Your endpoint must be reachable over HTTPS and answer quickly. Acknowledge first, process afterwards
Assume a delivery can arrive twice. Make handling idempotent
Webhooks belong to the direct API. They are not exposed through the MCP server
Direct API or MCP server?
| Direct API | MCP server |
You write code | Yes | No |
Conversational, driven by an AI assistant | No | Yes |
Webhooks | Yes | No |
Control over each individual request | Full | The assistant decides |
Base URL |
|
|
Credential | Same token | Same token |
Plenty of teams run both: MCP for exploring and ad hoc work, the direct API for anything scheduled or production-critical.
Access and limits
Availability and rate limits follow your EasyChannel subscription. A request refused on access or rate grounds usually means the plan does not include it or the calls are coming in too fast. Check the plan first, then the request rate.
Asking for more
Missing an endpoint? Open Settings > Integrations > API EasyChannel and click Need more API endpoints?. For MCP tools specifically, the MCP EasyChannel tile has its own Need more MCP tools? button. Both go straight to the EasyChannel team.
For anything else, easychannel.com/contact or your usual support channel.