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.

Quickstart

Make your first query

A copy-paste quickstart that searches by MPN and inspects the response shape.

This walks through one request: search by MPN and read back matching parts.

1. Send a search query

BASH

1curl -X POST https://graphql.zenode.ai/graphql \
2  -H "Authorization: Bearer <YOUR API KEY HERE>" \
3  -H "Content-Type: application/json" \
4  -d '{"query": "{ supSearchMpn(q: \"LM358\", limit: 5) { hits warnings results { description part { mpn manufacturer { name slug } } } } }"}'

Replace <YOUR API KEY HERE> with a key from zenode.ai/account/api.

2. Read the result

A successful response looks like:

JSON

1{
2  "data": {
3    "supSearchMpn": {
4      "hits": 5,
5      "warnings": [],
6      "results": [
7        {
8          "description": "…",
9          "part": {
10            "mpn": "LM358",
11            "manufacturer": {
12              "name": "Texas Instruments",
13              "slug": "texas-instruments-inc"
14            }
15          }
16        }
17      ]
18    }
19  }
20}

hits — number of parts in this page (up to limit).
warnings — human-readable strings when a parameter was ignored or only partially applied.
results — each item wraps a part plus a display description.

3. Add the fields you need

GraphQL returns only the fields named in the query. Add fields from the documented return types as your existing integration needs them.

Request only the fields you need. Adding sellers { company { name } } under part pulls distributor data without a second HTTP call.

Search queries — keyword search, filters, and aggregations
Usage billing — which queries cost API units
REST vs GraphQL — when to use each API

1. Send a search query

2. Read the result

3. Add the fields you need

Next