No advanced technical skills are required, simply follow the steps below:

Prerequisites

An active Ezus account (your login email and password) with a Premium Plan to have access to the API.
The Postman application installed (free to download at postman.com/downloads) or the web version. For more details, please see our article ✍️ Setting up Postman for your Ezus API calls

💡 Good to know: API authentication relies on two elements.

The API key (x-api-key) identifies your account
The token (Authorization: Bearer) authorizes each request.

The token is valid for 12 hours; after that, it must be regenerated.

Note: the API address is https://api.ezus.app. The api.ezus.io page corresponds only to the documentation.

Step 1 — Prepare the product update request

Updating a product is done via the products-upsert route.

POST method, URL: {{baseUrl}}/products-upsert (or directly https://api.ezus.app/products-upsert)`
Headers tab:
x-api-key → your API key
Authorization → Bearer followed by your token
Content-Type → application/json
Body tab → raw → JSON.

Example to update a product's title:

{ "reference": "PRODUCT_REFERENCE", "title": "New product title" }

💡 If you want to update your product information in a language other than your account's default language, you'll need to use the langs block.

For example, to update a product's title in French:

{ "reference": "PRODUCT_REFERENCE", "langs": [ { "lang": "french", "name": "French product name" } ] }

Key point: the reference

The reference field is the key that identifies the product to be updated. It corresponds to the "API field" column of your product export (and not to the "Product reference" column, which corresponds to the file number info_number).

⚠️ If the reference provided does not exist, the API will create a new product instead of modifying one; so always check the reference.

💡 Only the fields sent are modified: if you only send reference and title, the product's other information (price, category, descriptions, etc.) remains unchanged.

Step 2 — Test a single request

Before any bulk update, we recommend that you test on a single product:

Open a request, check the URL, the Headers and the Body.
Click Send.

In the Response area, you should see a 200 OK status and a response like:

{ "error": "false", "message": "ok", "action": "Product successfully updated", "reference": "PRODUCT_REFERENCE" }

Check in Ezus that the product has indeed been updated.

Step 3 — Update several products at once

To process many products, use a collection containing one request per product and launch the Collection Runner:

Hover over the collection name in the left-hand panel → click the ··· → Run collection.
Check that all the requests to be executed are ticked.
Leave a Delay of about 200 ms between requests.
Leave the "Stop run if an error occurs" option ticked: in the event of an error, execution stops, which makes it possible to identify the request concerned.
Click Start run. Each product is displayed with a Passed or Failed status.

Troubleshooting common problems

401 / 403 error: authentication problem. Check the API key and the token, and make sure there is no extra space. If the token is more than 12 hours old, regenerate it.
A new product was created instead of being updated: the reference sent did not match any existing product. Be sure to use the value from the "API field" column.
The langs block is rejected: the language concerned (e.g. "american") must be enabled on your Ezus account.

Update your catalog products via the API (Postman)