Skip to content

Articles

An Article is one row in your sales catalogue: a thing you sell, keyed by the article_number you assign in your source system. Articles are the most important resource in this API — Mercura matches every position on every incoming customer LV against your articles, so the quality of the offers you read back depends directly on the quality of the article catalogue you push.

You can:

  • POST /articles — bulk-upsert up to 100,000 articles in a single call. Async — returns a JobAck; poll GET /jobs/{job_id} for status. Rows with the same article_number as an existing row are updated in place; new rows are inserted. Recommend running this once per night with the full delta since the last successful job.
  • GET /articles — cursor-paginated list of your articles. Use modified_since on the first page to fetch only the rows that changed since your last sync.
  • GET /articles/{article_number} — fetch a single article by the partner-supplied article_number.
Operations

Data depth and match quality

The precision of Mercura's article matching depends directly on the depth and structure of the article data you push. The more you send, the more accurately Mercura can resolve incoming LV positions against your catalogue.

Articles that match well tend to carry:

  • Identifying attributes — manufacturer name and article number, supplier article number, EAN / GTIN.
  • Classifications — ETIM class, applicable norms (DIN / EN / ISO).
  • Technical parameters — power, voltage, dimensions, IP rating, and any other physical or electrical characteristics that distinguish one variant from another.

Any field your source system carries but the standard schema does not cover can be passed through the custom_fields attribute available on every master-data resource — no schema change required.