Skip to main content
Run these queries and mutations in the API Playground. To send one from your own client, such as an HTTP action in an automation tool, put the operation in the JSON request body’s query field as a string, and its variables in the variables field:
Find parts by part number or description substring:
Fetch a procedure template plus every step and its fields:
Find every recorded value of one field, on run steps with a given title, across runs that build a given part number:
List the build requirements on a unit’s as-built BOM:
Pull the as-built BOMs of two units and diff them client-side:
Get the runs that are to do or in progress. Each run’s _etag is the value an update mutation on that run needs:
Every run a specific part inventory has gone through, newest first:
List inventory units of a given part, with each unit’s location:
Get every serialized instance of a part with its current state:
All open issues, with each issue’s disposition type for triage:
Match each user’s numeric id to their name and email, such as to fill a setting that asks for user IDs or to read the user IDs in an export:
While hasNextPage is true, run the query again with after set to the endCursor from the previous page. For more information, see Paginate query results.
List the recorded changes to one part, such as edits to its reorder points, with when each change happened, who made it, and the fields it changed:
Verify your token and find which org you’re in: