Mirakl Connect

Mirakl Connect

This connector uses the Mirakl Connect API (https://miraklconnect.com/api), the seller-side channel platform where one company manages its stores on many marketplaces and sales channels from one place: orders from every connected channel, returns, order documents, customer conversations and the Connect product catalog with prices and stock. Shipping, cancelling and accepting order lines are included but installed switched off.

Not the same as the Mirakl Seller API: the separate Mirakl Seller API connector (mirakl) talks to one Mirakl-powered marketplace at a time (its own https://<marketplace>.mirakl.net/api, shop API key, OR/OF/P APIs). Mirakl Connect is the multi-channel layer above that: one login and one API for all your channels, with its own order ids, OAuth2 credentials and endpoints. Install this one when your company works in Mirakl Connect.

Setup (about 5 minutes)

1. Create OAuth2 API credentials for your company in Mirakl Connect, as described in Mirakl's guide Integrating with Connect APIs (Mirakl Connect help for sellers). You get a client ID and a client secret; the secret is shown once.
2. Paste them into MIRAKL_CONNECT_CLIENT_ID and MIRAKL_CONNECT_CLIENT_SECRET. AnythingMCP exchanges them at the Mirakl Authentication System (https://auth.mirakl.net/oauth/token, client credentials grant) for a bearer token of about one hour and renews it by itself.
3. Run mirakl_connect_list_orders to check the connection.

Workflow

• Orders: mirakl_connect_list_orders (filter by statuses, updated_from, fulfillment_type; 10 per page by default, up to 100), then mirakl_connect_get_order for one order by its Connect id. The sales channel and store of each order are in origin (channel_name, channel_store_name); the channel's own order number is channel_order_id. Without updated_from or ids, Mirakl returns the last 30 days.
• Catalog, offers and stock: mirakl_connect_list_products returns each product with standard_prices, discount_prices and stock quantities.
• After-sales: mirakl_connect_list_returns (needs updated_from), mirakl_connect_list_order_documents, mirakl_connect_list_conversations and mirakl_connect_get_conversation.
• Paging: every list answers next_page_token while more items exist; pass it as page_token.

Writes switched off: mirakl_connect_ship_order, mirakl_connect_cancel_order_lines and mirakl_connect_accept_order_lines act on the live sales channel, where the customer is notified and refunds happen, so an admin turns them on deliberately. Before each call show the user the order, the lines and the values and wait for a yes. Take the line ids from order_lines[].id of the order. These calls are asynchronous: they return an action_id; check the outcome with mirakl_connect_get_action_status, since the channel can still reject the action.

Channels: the Mirakl Connect API has no endpoint that lists your connected channels; read them from the origin of the orders.

Rate limits: Mirakl asks to call the order, return and product lists at most once per minute when syncing; 429 answers carry a Retry-After header. Dates are ISO 8601 with a zone.

Errors: 401 means the client ID or secret is wrong or the token expired; 403 means the API client lacks the scope for that call (e.g. connect:order:read, connect:shipment:create); 402 means the feature (for example conversations) is not part of the account's Mirakl Connect plan; 404 an unknown order or conversation id.