Platform support

See what ManoMano’s public partner docs say about a product file

ManoMano’s public Partners API page describes a REST API for orders, offers, ManoFulfillment product stock, categories, and brands. It explains how a Toolbox admin creates an API key. It does not publish a product CSV or a column list. The seller page lists manomano.fr, manomano.es, manomano.it, manomano.co.uk, and manomano.de. This is one page for that public documentation, not a copied file for each domain.

Documentation checked 1 November 2026 · English

Does ManoMano’s public documentation give you a product spreadsheet?

The Partners API page says the ecosystem is REST and lists Orders API (REST), Offers API, ManoFulfillment Product Stock API, Categories API, and Brands API. It says more APIs will be available later. Production requests go to https://partnersapi.manomano.com. Sandbox requests go to https://partnersapi.sandbox.manomano.com. The same page says sandbox APIs operate Monday 00:00–20:00 and Tuesday–Friday 07:00–20:00 (CEST), and that access is disabled at other times.

That page says the legacy Orders API (XML) has an end of life of 31 March 2025 and must be migrated to Orders API (REST). The separate XML status article says that from the end of February the XML Order API will be shut off, and it does not print a year. This page leaves those two sentences side by side. Neither page, nor the Offer API FAQ, publishes a catalog spreadsheet. The Manomano Feed category and the Mandatory Attributes Program category returned headings on 1 November 2026 and did not render article text, so they are not a column guide.

What do the rendered Offer and Orders pages actually limit?

The Offer API FAQ says update_offers allows 200 requests per hour per IP address, returns HTTP 429 when that limit is reached, and accepts a PATCH body of at most 5 MB. It says the request_id in a 207 Multi-Status response can be sent on a later GET to check each SKU. The page asks how to unfreeze offers with unfreeze_offers and does not render the steps under that heading. It does not list offer fields or a sample CSV row.

The Partners API page says an API key is created by a Toolbox user with the Admin role: Settings, API keys, Create API key, a name, Generate API key, then copy. It says that is the only time the key is shown. Requests send it as the x-api-key header. The brands example filters with name=MAKITA. That is a sample query on the page, not a required brand and not a spreadsheet column. The Orders section says requests might be limited to 250 per hour per API key, with HTTP 429 when the limit is reached, and that WAITING_PAYMENT is not currently available in Orders API (REST).

How do you handle a supplier file when the public docs are an API?

Keep a supplier CSV as your own notes. The public pages describe JSON requests to the partners API. They do not tell you to upload that CSV.
If Toolbox gives you a product file that these public pages do not document, download that file and map onto the headers it actually contains. Record the storefront domain on the contract. The seller page lists five domains and does not say they share one spreadsheet.
In Golanto, choose ManoMano. Record the domain and the date you read manomano.dev. The mapper still opens on Amazon until you change the platform.
Create an API key only in Toolbox, by the steps on the Partners API page, and keep it out of the spreadsheet and out of Golanto. The mapper compares columns. It does not call partnersapi.manomano.com.
Leave the Manomano Feed and Mandatory Attributes headings as unread article text. Do not fill the blank with guessed attributes, quotas, or column names.

Worked example

A supplier row is not a ManoMano partner request

Inspect this record

sku,title,price
DRILL-3,Cordless drill,129.00

These headings are a synthetic supplier sketch. The Partners API page does not name them. Its brands example uses the query name=MAKITA, which is a sample filter, not a column. The Offer API FAQ describes update_offers, a 5 MB PATCH limit, and a request_id from a 207 response. It does not show a CSV row. Do not rename this sketch and post it to the partners API.

What this check cannot establish

Golanto does not call the ManoMano API, create Toolbox keys, or open a seller contract. This page uses the Partners API page, the Offer API FAQ, the XML Order API status article, the seller page, and the Manomano Feed category, retrieved on 1 November 2026. The Feed category and the Mandatory Attributes Program category did not render article bodies. The API page dates the XML Orders end of life to 31 March 2025. The status article says the shutdown is from the end of February and prints no year. This page does not collapse those sentences into one date. No product-file header, import error, or cell color is stated here, because the rendered pages do not publish them. The five domains on the seller page are manomano.fr, manomano.es, manomano.it, manomano.co.uk, and manomano.de. A column map for one domain is not supplied by this page.

Check your file

Start with a copy. Review changes before downloading your import file.

Open the template mapper

Official references

Schema review: manomano-partners-api-2026-11-01. Examples are synthetic. Store-specific and unpublished requirements are outside these checks.

Common questions

Can I upload a product CSV from ManoMano’s public partner docs?

Those pages do not describe that upload. They describe REST APIs for orders, offers, ManoFulfillment stock, categories, and brands, plus an API key created in Toolbox. A supplier CSV stays your own notes unless Toolbox gives you a file these pages do not document.

Do the five ManoMano storefronts share this page’s file?

The seller page lists manomano.fr, manomano.es, manomano.it, manomano.co.uk, and manomano.de. The public API docs retrieved with it do not publish a spreadsheet for any of them. This page does not copy one guessed file across those domains. Record the domain on the contract you are filling.