GraphQL is for Nexar migration only
Use the GraphQL API only as a drop-in replacement for Nexar's GraphQL when migrating existing integrations. For new projects and full platform capabilities, use the REST API— it's the actively maintained, modern interface.
SupPart
Core part object returned from search, multi-match, and supParts.
Nested under results { part { … } } or returned directly from supParts and supMultiMatch.
Key fields
| Field | Type | Description |
|---|---|---|
id | ID! | Numeric catalog ID |
mpn | String! | Manufacturer part number |
name | String | Display name |
genericMpn | String | Generic MPN when applicable |
slug | String | Derived from MPN (lowercase, spaces → hyphens) |
zenodeUrl | String | https://zenode.ai/parts/{slug} when a canonical slug exists; otherwise empty |
shortDescription | String | One-line description |
descriptions | [SupDescription!] | Full description variants |
manufacturer | SupCompany | Manufacturer company |
documentCollections | [SupDocumentCollection!] | Datasheets and documents |
images | [SupImage!] | Part images |
specs | [SupSpec!] | Electrical and mechanical specifications |
category | [SupCategory!] | Part categories |
sellers | [SupPartSeller!] | Distributors and offers |
Many additional fields exist for API parity (e.g. similarParts, cadModels, akaMpns); several are placeholders or empty. Use GraphiQL to introspect the full schema.
Related
SupPartResultSet— search wrapper type- Parts by ID — fetch by numeric ID