--- title: Channable API Integration on Truto slug: channable category: E-Commerce canonical: "https://truto.one/integrations/detail/channable/" --- # Channable API Integration on Truto **Category:** E-Commerce **Status:** Generally available ## MCP-ready AI tools Truto exposes 23 tools for Channable that AI agents can call directly. - **list_all_channable_project_orders** — List all orders for a Channable project, sorted from most recent to oldest. Returns each order with id, price, and status. Supports filtering by status, date range, search text, and error status. Max 100 results per page. Required: company_id, project_id. - **channable_project_orders_cancel** — Cancel a Channable order by setting its status to cancelled and propagating the update to the involved marketplaces. Returns a response model confirming the cancellation result. Only covers seller-initiated cancellations; buyer-initiated cancellations require manual confirmation in the marketplace seller account. Required: company_id, project_id, order_id. - **channable_project_orders_attach_attachment** — Upload a PDF invoice attachment to a Channable order for asynchronous upload to the marketplace. Returns a 202 acknowledgment confirming the file has been processed and will be uploaded asynchronously. Currently only accepts PDF invoices. Required: company_id, project_id, order_id, file. - **get_single_channable_project_order_by_id** — Get a single Channable order by id, including its events. The order contains price breakdown, purchased products, and billing/shipping address information. Returns: id, channel_name, platform_name, project_id, order_config_id, platform_id, channel_id, status_paid, status_shipped, error, obfuscated, created, modified, retrieved_at, channel_id_internal, data, error_reason, fulfillments,…. Required: id, company_id, project_id. - **list_all_channable_project_anonymous_orders** — List anonymized orders for a Channable project with all personally identifiable information (PII) removed. Returns each order with order_id, status, price, and products. Max 100 per page. Required: company_id, project_id. - **create_a_channable_order_return** — Manual Return. Returns: status, message, response, id, data. Required: order_id, project_id, company_id, products. - **create_a_channable_orders_test** — Create one or more test orders containing fake data in Channable for a specific order config. Returns a dynamically-structured response (attributes) whose specific fields are not documented upstream. A JSON request body is expected. Not intended for automated processes; may change without notice. Required: company_id, project_id, order_config_id. - **create_a_channable_order_shipment** — Shipment. Returns: status, message, response, id, data, channable_order_id. Required: company_id, project_id, order_id. - **create_a_channable_order_manual** — Manual. Returns: status, message, response, id, data. Required: company_id, project_id, order_id. - **list_all_channable_project_offers** — List offers (product updates) for a Channable project, sorted from most recent to oldest. Returns: id, project_id, client_id, gtin, stock, stock_tracking, availability, title, price, created, modified. Max 100 results per page. Required: company_id, project_id. - **create_a_channable_project_offer** — Stock Updates Update (Deprecated). Returns: status, message, content. Required: company_id, project_id. - **create_a_channable_project_stock_update** — Update offers' stock for a selected Channable project and propagate the changes to all connected marketplaces. Returns a stock update response confirming the update. Required: company_id, project_id. - **list_all_channable_project_returns** — List all returns for a Channable project, sorted from most recent to oldest. Returns: id, project_id, created, modified, retrieved_at, error, platform_id, platform_name, channel_id, channel_name, log, status, data, obfuscated. Supports text search, date-range filtering, and a download mode; max 100 results per page. Required: company_id, project_id. - **get_single_channable_project_return_by_id** — Get a single Channable return by id. Returns: return. Required: id, company_id, project_id. - **list_all_channable_project_anonymous_returns** — List anonymized returns for a Channable project with all personally identifiable information removed. Returns: id, project_id, created, modified, retrieved_at, error, platform_id, platform_name, channel_id, channel_name, log, status, data. Identical to the /returns endpoint but with PII stripped from the return data; supports text search and date-range filtering. Required: project_id. - **create_a_channable_returns_test** — Create one or more test returns in Channable. Returns the created test return response object. Required: project_id, order_id. - **update_a_channable_return_status_by_id** — Update the status of a return in Channable, propagating the change to the involved marketplace. Depending on the new status, the end customer may or may not receive a refund. Returns the update return status response object whose fields are defined by the upstream Channable API schema (UpdateReturnStatusResponse). Required: return_id, project_id, company_id, status. - **get_single_channable_order_attachment_by_id** — Get the download URL for a Channable order attachment by id. Returns: url. The download URL is valid for 5 minutes. Required: id, company_id, project_id, order_id. - **get_single_channable_transporter_by_id** — Get the marketplace-specific transporters matching a Channable transporter code in Channable. Returns: channels. Valid transporter codes are listed by the /transporters/all endpoint. Required: id. - **list_all_channable_transporters** — List all Channable transporters with their standardized codes and labels. Returns: transporters. Use these standardized transporter codes when submitting order shipments. - **channable_transporters_list_for_channel** — Transporters For Channel. Returns: transporters. Required: channel. - **list_all_channable_statistics_orders** — List order statistics for all order configs in a Channable project for a given time frame. Returns a data object containing per-config statistics (orders, ordered products, commission, shipping costs, revenue, currency, daily revenue) and project-wide aggregated totals. Required: project_id, company_id. - **get_single_channable_statistics_order_by_id** — Get order statistics for a specific order config in a Channable project for a given time frame. Returns a data object containing cumulative counts (order revenue, shipping costs, commission) and daily counts (order revenue, shipping costs, commission, number of orders, number of ordered products). Required: id, project_id. ## How it works 1. **Link your customer's Channable account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app. 2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request. 3. **Call Truto's API to reach Channable.** The Proxy API is a 1-to-1 mapping of the Channable API. 4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field. ## Use cases - **Sync marketplace orders into ERPs and IMS platforms** — Inventory and ERP platforms can ingest orders from every marketplace a merchant sells on through a single Channable connection, then push stock updates back to prevent overselling on strict channels like Amazon and eBay. - **Unify returns and refunds inside helpdesk software** — Support platforms can surface marketplace returns directly in agent workflows and let agents approve or reject refunds without logging into individual seller portals, cutting ticket resolution time. - **Automate shipment tracking from WMS and shipping tools** — Fulfillment platforms can fetch marketplace-approved carrier codes and push tracking numbers back to Channable, satisfying on-time shipping metrics that protect seller account health. - **Power GDPR-safe ecommerce analytics** — BI and revenue analytics tools can pull anonymized order data and aggregated statistics to calculate cross-channel ROAS and margins without inheriting PII storage liability. - **Enable multichannel listing and offer management** — Product catalog and PIM tools can create offers on Channable projects to distribute listings across 2,500+ marketplaces from a single interface inside their own product. ## What you can build - **Cross-marketplace order ingestion** — Pull orders from every connected marketplace into your product using a single normalized order list and detail endpoint. - **Real-time multi-channel stock sync** — Push stock updates from your platform out to every marketplace a merchant sells on with a single API call per SKU. - **Shipment dispatch with carrier mapping** — Fetch valid channel-specific transporter codes and send tracking numbers back to marketplaces automatically when labels are generated. - **Return management workflows** — List and inspect returns across marketplaces and update return status to trigger refunds on the origin channel from inside your UI. - **Marketplace invoice attachment automation** — Automatically attach PDF invoices to orders on marketplaces that require them, generated from your billing or accounting module. - **Anonymized analytics pipelines** — Feed anonymized order data and statistics into your BI product to calculate revenue, commissions, and shipping costs without handling buyer PII. ## FAQs ### How does authentication work for Channable through Truto? Channable uses API tokens scoped to a company and project. Truto handles token capture, storage, and injection so your end users complete a guided connection flow and your product receives authenticated API access without you managing credentials. ### Can we receive new orders in real time or do we have to poll? Channable's public API is primarily request-based, so ingestion typically relies on polling the order list endpoint on a schedule. Truto can manage scheduled syncs and deliver changes into your product on your preferred cadence. ### Which operations are supported today? The current integration covers orders (list, get, cancel, attach, manual create, test), shipments, returns (list, get, status update, test, anonymized list), offers, stock updates, transporters (including per-channel lists), order attachments, and statistics endpoints. ### How do we handle marketplace-specific carrier codes for shipments? Use the transporters endpoints to fetch the list of valid carriers, including the per-channel list, so you can map internal carriers to codes each destination marketplace accepts before pushing tracking data via the shipment endpoint. ### Can we build analytics without storing buyer personal data? Yes. Channable exposes anonymized order and return endpoints as well as dedicated statistics endpoints, so BI use cases can operate on PII-stripped data and stay within GDPR scope. ### What if we need a capability that isn't in the current tool list? Truto builds additional endpoints on request. If your product needs a Channable resource or action not yet exposed, we can add it to the integration without you writing or maintaining the client code. ## Related reading - [Connect Channable to ChatGPT: Sync Orders, Stock & Returns](https://truto.one/blog/connect-channable-to-chatgpt-sync-orders-stock-returns/) — Learn how to connect Channable to ChatGPT using Truto's auto-generated MCP server. Sync orders, manage returns, and automate stock updates with AI. - [Connect Channable to Claude: Analyze Sales & Manage Shipments](https://truto.one/blog/connect-channable-to-claude-analyze-sales-manage-shipments/) — Give Claude secure read and write access to Channable using a managed MCP server. Automate shipments, analyze multi-channel order statistics, and sync stock. - [Connect Channable to AI Agents: Automate Fulfillment Workflows](https://truto.one/blog/connect-channable-to-ai-agents-automate-fulfillment-workflows/) — Learn how to connect Channable to AI agents using Truto's /tools endpoint. Build autonomous fulfillment workflows, sync orders, and manage stock natively.