Skip to main content
GraphQL API for Duro PLM v1, the legacy Duro platform at mfg.duro.app. Use when a customer’s Duro lives at mfg.duro.app (component links look like mfg.duro.app/component/view/); customers on the new platform, durohub.com, connect the separate “Duro Design” provider (duro) instead. Query and manage the v1 data model: components, products, component trees/revisions, categories, change orders, libraries, and webhooks, with create/update/delete mutations. Every request is a POST to https://mfg.duro.app/graphql with the operation in the body; see the routing hint for the v1 query shapes, which differ from Duro Design’s. 7 example endpoints available through Lava’s AI Gateway. See the Duro PLM v1 API docs for full documentation.
This provider requires your own credentials — connect your API key or OAuth account before use.
This is a catch-all provider — any valid URL under https://mfg.duro.app/graphql is supported. Duro PLM v1 (legacy) GraphQL API. Single endpoint: POST https://mfg.duro.app/graphql with a JSON body containing a “query” string and optional “variables”. Auth is supplied automatically (apiToken header). The v1 schema differs from Duro Design: list queries are top-level and wrap results in connection envelopes, e.g. components(libraryType: GENERAL) { connection(first: N, after: cursor) { totalCount pageInfo { hasNextPage endCursor } edges { cursor node { id name } } } }. Lookups by id use plural ByIds queries: componentsByIds(ids: […]), productsByIds, changeOrdersByIds, categoriesByIds, componentRevisionsByIds, productRevisionsByIds. Other queries: componentTreeById / componentTreeByIds (assembly trees), products, changeOrders, categories, libraries, tokenActiveLibrary (which library the token operates in; the “hello world” auth check), userById, webhooksByIds, apiToken (mints a fresh 90-day token from the current one). Mutations: createComponent, updateComponent, deleteComponent, createProduct, updateProduct, deleteProduct, createChangeOrder, updateChangeOrder, deleteChangeOrder, createDocuments, deleteDocuments, createWebhook, deleteWebhookById, updateCategories, and change-order approval template CRUD. IDs are 24-char hex strings (mfg.duro.app/component/view/{id} in the web app). Full reference: https://mfg-core-api.duro.app/docs/. ITAR-hosted customers (app.govduro.us) are not routed by this provider. The endpoints below are curated examples.

Endpoints

Show which library the connected token operates in. Use as the auth/connectivity check (the “hello world” query).

POST https://mfg.duro.app/graphql — Free

List components in the company (GENERAL) library with relay pagination. Sortable by name, date, mass, revision, category.

POST https://mfg.duro.app/graphql — Free

Fetch components by their 24-char hex ids, including CPN, children (BOM), and revision history.

POST https://mfg.duro.app/graphql — Free

Fetch the full assembly tree (BOM hierarchy) for a component by id.

POST https://mfg.duro.app/graphql — Free

List products (top-level sellable assemblies) with relay pagination.

POST https://mfg.duro.app/graphql — Free

List change orders (ECOs) with relay pagination.

POST https://mfg.duro.app/graphql — Free

Mint a fresh 90-day API token using the currently connected token. Reconnect with the returned value before the old one expires.

POST https://mfg.duro.app/graphql — Free

Next Steps

All Providers

Browse all supported AI providers

Forward Proxy

Learn how to construct proxy URLs and authenticate requests