Integration

Channable integration

Channable connects a webshop to marketplaces (Amazon, Bol, eBay, Zalando and more). This order connection API lists and reads marketplace orders and returns of a Channable project, pushes shipment (track and trace) and cancellation updates back to the marketplaces, updates offer stock across every marketplace of a project, handles return statuses, uploads PDF invoices to orders, lists supported transporter codes and reads order statistics. Every project route needs your company_id and a project_id, both shown in the Channable app. Feed, product and listing management are not part of this API, and the deprecated v1 order reads and stock route are left out. Authentication is a company API token (generated by a company owner in Company settings, Channable API) sent as Authorization: Bearer.

Connect Channable How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Channable.Built from the 22 Channable tools below, on the connection you add once.

What you can do with Channable

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Order, 4 operations

get_orderGet orderGETReturns one order with its events, fulfillments and attachments. Addresses come either as street, house_number, house_number_ext and address_supplement, or as address1 and address2. Each product price is per unit.
get_order_config_statisticsGet order config statisticsGETReturns statistics of one order connection for a time frame: cumulative and daily revenue, shipping costs and commission, plus daily numbers of orders and ordered products.
get_order_statisticsGet order statisticsGETReturns order statistics of a project for a time frame: per order connection and in total, the number of orders and products, commission, shipping costs, revenue, currency and daily revenue points.
list_ordersList ordersGETLists the orders of a project, most recent first, with paging (limit up to 100, offset) and filters on status, errors, a search term and date ranges (UTC). Returns total, error_count and the orders.

Return, 3 operations

create_order_returnCreate order returnPOSTCreates a return on the marketplace for products of an order. Only Fruugo, Otto, Veepee and Zalando support it. Each product needs its id and quantity; status is accepted (default) or rejected.
get_returnGet returnGETReturns one return of a project: its status, the returned item, the reason, the customer and address data, and the marketplace references.
list_returnsList returnsGETLists the returns of a project, most recent first, with paging (limit up to 100, offset) and filters on status, errors, a search term and date ranges (UTC). Returns total, error_count and the returns.

Attachment, 2 operations

get_order_attachment_urlGet order attachment urlGETReturns a download URL for an order attachment (an invoice uploaded with upload_order_invoice). The URL is valid for 5 minutes.
upload_order_invoiceUpload order invoicePOSTUploads a PDF invoice (base64) to the marketplace and links it to the order or some of its items. A 202 answer means the file was accepted and is uploaded asynchronously. Only marketplaces listed in the Channable docs support it.

Test, 2 operations

create_test_orderCreate test orderPOSTCreates test orders with fake data in a Channable Sandbox order connection, for testing an integration. Every field is optional and overrides the sandbox defaults. The vendor says not to use it in automated processes.
create_test_returnCreate test returnPOSTCreates a test return for an existing Channable order, for testing an integration with the Channable Sandbox.

All, 1 operation

list_transportersList transportersGETLists every standardized Channable transporter code with its label. Use one of these codes as transporter when calling update_order_shipment.

Anonymous order, 1 operation

list_anonymized_ordersList anonymized ordersGETSame listing as list_orders but with all personally identifiable information removed from the order data. Supports search, date ranges (UTC), limit (up to 100) and offset.

Anonymous return, 1 operation

list_anonymized_returnsList anonymized returnsGETSame listing as list_returns but with all personally identifiable information removed from the return data. Supports search, date ranges (UTC), limit (up to 100) and offset.

Cancel, 1 operation

cancel_orderCancel orderPOSTCancels an order (or some of its items) as the seller and propagates it to the marketplaces. Omit order_item_ids to cancel the whole order. A buyer cancellation must be confirmed in the marketplace seller account instead.

Channel, 1 operation

list_channel_transportersList channel transportersGETLists the transporters a marketplace (channel) supports, each with its label and the country it applies to (ALL for every country).

Manual, 1 operation

set_order_manualSet order manualPOSTMarks an order as handled manually: Channable takes no further action on it after this call.

Offer, 1 operation

list_stock_updatesList stock updatesGETLists the stock updates (offers) you posted to a project with update_stock, most recent first, with their stock, gtin, title and timestamps. Shown under Orders, Product updates in the Channable app.

Shipment, 1 operation

update_order_shipmentUpdate order shipmentPOSTMarks an order (or some of its items) as shipped with track and trace details, and propagates it to the marketplace. Omit order_item_ids to ship the whole order. Spartoo and Veepee do not support partial shipments.

Status, 1 operation

update_return_statusUpdate return statusPOSTSets the status of a return and propagates it to the marketplace. Depending on the status the end customer does or does not get their money back.

Stock update, 1 operation

update_stockUpdate stockPOSTSets the stock of up to 50 offers of a project and propagates it to every marketplace of that project. Each item needs id and stock (the whole new stock value, not a delta); title and gtin are only for display.

Transporter, 1 operation

get_transporter_channelsGet transporter channelsGETReturns, per marketplace, the marketplace-specific transporters (label and country) that a Channable transporter code maps to.

Use Channable from Claude Code, Cursor or Codex

Connect Channable in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Channable operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Channable

Create your workspace
Sign up free. Nothing to install.
Connect Channable once
Add your Channable connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.