Mirakl as a Channel

July 2, 2026

Summary

Mirakl is a marketplace platform that many major retailers (Best Buy, Lowe's, Kohl's, Macy's and others) use to run their seller marketplaces. Flxpoint connects to a retailer's Mirakl instance with an API Key and Base URL and supports Sync & Link Listings, Publish Listings, Get Orders, and Sync Orders. Because each retailer runs its own independent Mirakl instance, you create a separate Flxpoint channel connection for each marketplace you sell on.

What this integration does

Publish Listings

Creates new offer listings on the retailer's Mirakl marketplace

Sync & Link Listings

Syncs price, quantity and status to the retailer's Mirakl catalog for linked offers

Get Orders

Imports orders from the retailer's Mirakl marketplace into Flxpoint

Sync Orders

Pushes shipment tracking back to the retailer's Mirakl marketplace

How to connect - credentials you need

Go to Sales Channels and click + Add Channel to open the Channel Wizard. Choose Mirakl, name the channel, and select the processes you want (Sync Listings, Publish Listings, Get Orders, Sync Orders). In the Connect Channel step enter the values below, then click Test Connection → Save Connection and finish with Confirm Integrations.

Connection NameSetting

A label for this connection inside Flxpoint (e.g. Best Buy Mirakl). Use the retailer name so it is clear which marketplace this channel connects to.

For your own reference only – it is not sent to Mirakl.

API KeyRequired

The API key generated in the seller/supplier portal of the specific retailer marketplace you are integrating with (e.g. Best Buy's seller portal, Lowe's supplier portal) – not from Mirakl's own website.

Generated in your seller account settings on the retailer's Mirakl portal.

Base URLRequired

The API endpoint for that retailer's Mirakl instance, e.g. https://bestbuy.mirakl.net. Enter the full HTTPS URL with no trailing path.

Specific to the retailer's Mirakl instance; each retailer has a different Base URL.

Can't find the API Key or Base URL? They come from the specific retailer's Mirakl seller/supplier portal, not from Mirakl directly. Contact your retailer account manager or marketplace onboarding team if you are unsure where to locate them. If the connection test fails, regenerate the API Key in the retailer portal and confirm the Base URL is the correct HTTPS endpoint for that retailer.

Important - read before configuring

Each Mirakl-powered retailer requires a separate channel connection

Mirakl is an underlying platform – Best Buy, Lowe's, Kohl's and Macy's each operate their own independent Mirakl marketplace with a unique Base URL and API Key. Create a separate Flxpoint channel for each retailer marketplace you sell on. A single Mirakl connection cannot cover multiple retailer storefronts, and products published to one retailer's instance are not visible on another's.

The API Key comes from the retailer's Mirakl seller portal, not from Mirakl directly

Your API Key is generated in the seller/supplier portal of the specific retailer marketplace (e.g. Best Buy's seller portal, Lowe's supplier portal). The Base URL is also specific to that retailer's Mirakl instance. Contact your retailer account manager or marketplace onboarding team if you cannot locate these credentials.

Mirakl Connect and Mirakl Direct are different – Flxpoint uses Mirakl Direct

Some retailers use Mirakl Connect (a separate app-based integration layer) rather than a standard Mirakl Direct API connection. The Flxpoint Mirakl channel uses the Mirakl Direct API. Many retailers on Mirakl Connect still expose a Direct API endpoint; if your retailer requires Mirakl Connect specifically, confirm with Flxpoint support whether your configuration is compatible before connecting.

Sync Orders needs Carrier and Tracking Number mapped for tracking to reach the retailer

For shipment tracking to update in the retailer's Mirakl marketplace, Sync Orders must be configured and the Carrier and Tracking Number fields must be mapped in the Sync Orders template. If these fields are missing, orders stay in an unshipped state in the retailer portal, which can trigger late-shipment notices. Verify your Sync Orders mapping before the first live order.

Mapping - fields to know

Publish Listings Sync & Link Listings Get Orders Sync Orders

Creates new offer listings on the retailer's Mirakl marketplace. Offers match to existing catalog products via EAN, UPC, or a retailer-specific product identifier, so the identifier in your Flxpoint listing must match the exact value in the retailer's Mirakl catalog. Each retailer defines its own required category attributes, and some marketplaces require seller approval for specific product categories before offers can be created.

Syncs price, quantity and status to the retailer's Mirakl catalog for offers that are already published/linked. Run this on a schedule to keep your live offers current; use Publish Listings first to create the offers, then Sync & Link to maintain them.

Imports orders from the retailer's Mirakl marketplace into Flxpoint. The order status filter in Get Orders settings must match the status labels used by that retailer's Mirakl instance – labels vary by retailer (e.g. some use WAITING_ACCEPTANCE, others use SHIPPING). Confirm the date-range window covers the orders you expect.

Pushes shipment tracking back to the retailer's Mirakl marketplace so the order is marked shipped. The Carrier and Tracking Number fields are required in the Sync Orders mapping template – if they are unmapped, tracking will not update and the order stays unshipped in the retailer portal.

Common issues

Connection test fails – invalid API Key or Base URL

Confirm both values come from the correct retailer's seller portal – not from a different retailer's Mirakl instance and not from Mirakl's own website. The Base URL must be the specific HTTPS API endpoint for your retailer (e.g. https://bestbuy.mirakl.net) with no trailing path, and the API Key must belong to your active seller account on that marketplace. Regenerate the API Key in the retailer portal if you are unsure it is still valid.

Publish listing stuck or unable to publish to the Mirakl marketplace

Check the job logs for the specific Mirakl API error. Common causes: the offer's category or attribute set does not match what the retailer's catalog expects (each retailer defines its own required fields); the SKU is already published under a different offer ID and conflicts; or the marketplace requires seller approval for that product category. Confirm with your retailer account manager that your seller account has permission for the category you are publishing.

Sync Orders not pushing tracking – order remains unshipped in the retailer portal

Verify the Sync Orders template has Carrier and Tracking Number mapped – both are required for Mirakl to mark an order shipped. Confirm the Sync Orders job has run after the order was fulfilled in Flxpoint (check the last-run timestamp). If the job ran cleanly but tracking still did not appear, check the logs for a silent Mirakl API rejection and open a support ticket with the order number.

Items publishing to the wrong product or appearing incorrectly on the marketplace

Mirakl-powered marketplaces match offers to existing catalog products via EAN, UPC, or a retailer-specific product identifier. If an offer lands on the wrong product page, the identifier in your Flxpoint listing does not match the correct product in the retailer's catalog. Verify the EAN/UPC/SKU matches the exact value in the retailer's Mirakl catalog, and confirm the required identifier format with your retailer account manager.

Orders not importing from Mirakl into Flxpoint

Run Test Connection to confirm the API Key is still valid – some retailer configurations rotate or expire keys. Confirm the Get Orders job is scheduled and check its last-run timestamp. Verify the order status filter matches the statuses used by that retailer's Mirakl instance (labels vary, e.g. WAITING_ACCEPTANCE vs SHIPPING). If the connection is valid and the job runs without errors but returns nothing, confirm orders exist in the seller portal and that the date-range window covers them.

Get Orders fails – "Mirakl API unavailable due to Cloudflare DNS error (error 1016)"

This means the retailer's Mirakl marketplace domain has a broken DNS/Cloudflare configuration on their end – Cloudflare itself flags the error with owner_action_required: true and retryable: false, meaning retrying the job will not resolve it. This is not a Flxpoint connection issue; the retailer (or whoever manages their Mirakl domain's DNS/Cloudflare setup) needs to fix it before Get Orders can succeed again.

FAQs

Where do I get the API Key and Base URL to connect a Mirakl channel?▸

Both credentials come from the specific retailer's seller or supplier portal – not from Mirakl's main website. For Best Buy, log into the Best Buy marketplace seller portal and find the API credentials section; for Lowe's, use the Lowe's supplier portal. The Base URL is the API endpoint for that retailer's Mirakl instance (e.g. https://bestbuy.mirakl.net) and the API Key is generated in your seller account settings. Contact your retailer account manager or onboarding team if you cannot locate them.

Can I use one Mirakl channel connection to sell on both Best Buy and Lowe's?▸

No – Best Buy and Lowe's each run their own independent Mirakl marketplace with different API endpoints and credentials. You must create a separate Flxpoint channel for each retailer, and each channel has its own connection settings, listing operations and order flows. Products published to one retailer's Mirakl instance are not automatically visible on another's.

Does Flxpoint support Mirakl Connect (used by retailers like Best Buy and Kohl's)?▸

The Flxpoint Mirakl channel uses the Mirakl Direct API. Mirakl Connect is a separate app-based layer some retailers offer. Many retailers who use Mirakl Connect still expose a Mirakl Direct API endpoint that Flxpoint can connect to. If your retailer specifically requires Mirakl Connect and does not support a direct API connection, contact Flxpoint support to confirm compatibility before setting up the channel.

What operations does the Mirakl channel support?▸

The channel supports Sync & Link Listings (sync price, quantity and status to the retailer's Mirakl catalog), Publish Listings (create new offer listings on the marketplace), Get Orders (import orders from the retailer's Mirakl marketplace into Flxpoint), and Sync Orders (push shipment tracking back to the marketplace). Select the processes you need when creating the channel in Flxpoint.

How do I verify the Mirakl connection is working correctly before going live?▸

After entering credentials, use the Test Connection button during setup to confirm the API Key and Base URL are valid. Once connected, run each process manually on a small test set before enabling schedules – publish one known-good SKU, import a test order, and trigger a Sync Orders run to confirm tracking reaches the retailer portal. Verify directly in the retailer's Mirakl seller portal that the test listing and tracking appear as expected before turning on full automation.

Back to Marketplace & eCommerce Integrations