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.
SupPartResultSet
Fields, warnings, and aggregation resolvers on the search result set.
Returned by supSearchMpn and supSearch.
Fields
| Field | Type | Description |
|---|---|---|
hits | Int! | Number of parts in this page |
results | [SupPartResult!]! | List of matched parts with display metadata |
warnings | [String!]! | Ignored or partially applied parameters |
specsViewAttributeGroups | JSON | Spec attributes grouped for UI-style specs view |
suggestedCategories | JSON | Category suggestions (may be empty) |
suggestedFilters | JSON | Filter suggestions (may be empty) |
allFilters | JSON | Available filters (may be empty) |
appliedCategory | JSON | Applied category metadata |
appliedFilters | JSON | Applied filter metadata |
Aggregation resolvers
| Field | Arguments | Description |
|---|---|---|
specAggs | attributeNames: [String!]!, specAggSize (default 10) | Spec value buckets for named attributes |
manufacturerAgg | size (default 10) | Manufacturer buckets with counts |
categoryAgg | size (default 10) | Category buckets with counts |
Related
SupPart— nested underresults { part { … } }- Search queries — usage and examples