Make your first call
A copy-paste quickstart that matches an MPN and reads back the canonical part identifier you use everywhere else in the API.
This walks through a single request: take a part number and resolve it to a canonical Zenode part.
1. Send a match request
BASH
1curl https://api.zenode.ai/v1/parts/match \2 -H "Authorization: Bearer zk_live_xxxxxxxxxxxxxxxxxxxxxxxx" \3 -H "Content-Type: application/json" \4 -d '{5 "query": "TL072CP",6 "manufacturer": "TI"7 }'2. Read the result
JSON
1{2 "query": "TL072CP",3 "ambiguous": false,4 "results": [5 {6 "part": {7 "mpn": "TL072CP",8 "mpn_slug": "TL072CP",9 "manufacturer": {10 "slug": "texas-instruments-inc",11 "name": "Texas Instruments"12 },13 "description": "Dual JFET-Input Low-Noise Operational Amplifier, 8-PDIP",14 "image": "https://cdn.zenode.ai/blobs/documents/3f8a...e1.jpg",15 "status": "active",16 "url": "https://zenode.ai/part/texas-instruments-inc/TL072CP"17 },18 "confidence": 99,19 "exact": true20 }21 ],22 "request_id": "req_8f3a..."23}Because the query resolved cleanly, ambiguous is false and the single result is exact — you can
safely auto-accept results[0].
3. Use the identifier
A part is identified by the pair (manufacturer.slug, mpn_slug). Pass it to other endpoints — for
example, fetch the full record:
BASH
1curl https://api.zenode.ai/v1/parts/texas-instruments-inc/TL072CP \2 -H "Authorization: Bearer zk_live_xxxxxxxxxxxxxxxxxxxxxxxx"Store the (manufacturer.slug, mpn_slug) pair, not the human url. The url is for linking a
person to the Zenode web page; the slugs are the programmatic identifier.
Next
- Identifiers — how slugs work
- Part matching — single and batch (BOM) matching
- Part Catalog search — query + parametric filters