ZenodeZenode
Endpoints

Part detail

Full part records by slug

Fetch the full PartDetail for a single part.

parts:read
GEThttps://api.zenode.ai/v1/parts/{manufacturer}/{mpn}

The two path segments are the part's (manufacturer slug, mpn_slug) pair — both are required, since the same MPN can exist under different manufacturers (see Identifiers).

ParameterTypeRequiredDescription
manufacturer
stringRequiredManufacturer slug, e.g. texas-instruments-inc
mpn
stringRequiredThe part's mpn_slug (URL-safe MPN), not the raw mpn

Try it

Try itGET
Parameters

Manufacturer slug

The part's mpn_slug

Request
cURL
curl -X GET "https://ix.zenode.ai/zenode-api/v1/parts/texas-instruments-inc/TL072CP" \
-H "Authorization: Bearer <YOUR_API_KEY>"

Example

cURL
1curl https://api.zenode.ai/v1/parts/texas-instruments-inc/TL072CP \
2-H "Authorization: Bearer zk_live_xxxxxxxxxxxxxxxxxxxxxxxx"

Response

JSON
1{
2"part": { /* PartDetail see Objects */ },
3"request_id": "req_7d55..."
4}
ParameterTypeRequiredDescription
part
PartDetailRequiredThe full part record
request_id
stringRequiredFor support / tracing

Case handling

Lookups are exact-case first. If the exact case isn't found but a single part matches case-insensitively, the request redirects (308) to the canonical-case URL. A 404Not Found not_found is returned when nothing matches. Storing the exact mpn_slug Zenode returns avoids the redirect hop.

Next