GraphQL is for Nexar migration only
GraphQL overview
The GraphQL API exposes Zenode's parts data through a single endpoint with precise field selection and nested aggregations.
The Zenode GraphQL API is a query-driven interface for electronic parts data. Request only the fields you need, run aggregations on search results, and match many BOM lines in one round trip.
Endpoint
1POST https://graphql.zenode.ai/graphqlAll requests are POST with a JSON body containing query and optionally variables.
What you can do
Search by MPN or keyword
supSearchMpn and supSearch return ranked parts with optional manufacturer, category, and spec aggregations.
Match a BOM
supMultiMatch resolves many BOM lines in one request — MPN, SKU, or free-text per line.
Fetch parts by ID
supParts loads full part records when you already have numeric catalog IDs.
Manufacturers & categories
supManufacturers and supCategories list catalog metadata — free to call, no usage billing.
Schema at a glance
All root queries live on Query. Field names use camelCase.
| Query | Primary input | Return type | Billing |
|---|---|---|---|
supSearchMpn | q (MPN) | SupPartResultSet | Paid |
supSearch | q (keyword) | SupPartResultSet | Paid |
supMultiMatch | queries (BOM lines) | [SupPartMatch!]! | Paid |
supParts | ids | [SupPart!]! | Paid |
supManufacturers | ids / slugs | [SupCompany!]! | Free |
supCategories | ids / paths | [SupCategory!]! | Free |
See Usage billing for how paid queries meter against your plan, and Rate limits & usage for throttling and quota behavior.
How requests work
- Authentication is a Bearer API key on every request (see Authentication).
- Responses are JSON with
dataand/orerrors(GraphQL standard). - Paid queries may include
warningswhen parameters are partially supported or results are quota-capped. - Billing failures return GraphQL errors with an
extensionsobject — see Errors.
GraphQL complements the REST API: use REST for simple scripting with curl, use GraphQL when you need field selection, aggregations, or multi-part BOM matching in one request.
Next
- Authentication — create a key (shared with REST)
- Make your first query — copy-paste curl and GraphQL
- Search queries — MPN, keyword, and aggregations
- Return types —
SupPartResultSet,SupPart, and more