The company that makes a part, and the names it is known by.
Manufacturer names are how incoming part data is tied to the parts already in your library, so the same company written five different ways must resolve to one manufacturer. Each manufacturer therefore has one primary name plus any number of alternative_names — aliases such as TI for Texas Instruments, or a spelling your ERP happens to use. Aliases match exactly like the primary name.
Two kinds. Most manufacturers come from a shared public catalogue and are the same for every tenant. Manufacturers you import are private to your tenant. Only private manufacturers can be renamed; aliases, by contrast, are always private and can be added to public manufacturers too.
Matching is reported explicitly rather than left implicit. Every match carries a match_reason saying how closely the value matched (exact, normalized — ignoring case, punctuation and legal-form suffixes — or prefix) and which field it matched (the primary name or a specific alternative name). Prefix matches are informative only: they are never treated as duplicates, so importing Acme does not collide with an existing Acme Components.
Use POST /manufacturers/find to resolve names you already have, and POST /manufacturers/import to create the ones that did not resolve.
Look manufacturers up by name or alias.
Every requested value is matched against both primary manufacturer names and alternative names, using exact, normalized and prefix matching. Results come back in request order, one per requested name, with an empty matches list where nothing matched — so a result is never missing for a requested name.
Each match reports why it matched through match_reason, which distinguishes how closely the value matched (method) from what it matched against (matched_field). Prefix matches are informative only: they are deliberately never treated as duplicates when importing.
curl -i -X POST \
https://api.luminovo.com/manufacturers/find \
-H 'Accept: application/api.luminovo.manufacturer-v1+json' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"names": [
"string"
]
}'- object
- object (2)
{ "results": [ { … } ] }