Building an integration

Yantra Bhavan has a public, versioned API for software that works on a seller's behalf: a workshop's own ERP or MES, an internal script, or a tool you build for many sellers. It uses OAuth2 client credentials, and every route is scoped.

Getting a credential

Credentials are issued by the seller, not by us. An Owner or Manager opens Slicer connections, chooses Connect, picks Third-party software, and gives you the one-time enrolment code it shows. Your software redeems that code once for a client ID and secret. The credential is bound to that one shop and acts as the seller who created it.

What a third-party credential can do

• integration:parts:write
• integration:quotes:read
• integration:quotes:submit
• integration:rfq:read
• integration:files:read
• integration:orders:write — only when the seller ticks Can create orders; see order API and webhooks

A slicer's print-host key is a different kind, holding only integration:slice:upload. It is for slicers, not for code — see sending a slice back.

Reference

• The live API reference (OpenAPI), listing every public route with its scope.
• The contract package, @yb/integration-contract, holds the scopes, units, statuses and error shapes, and its README walks through enrolment, tokens and every route. A generated Node client, @yb/integration-sdk, sits beside it. Neither is on a public registry yet — ask us for access.

Handling seller data

A quote includes the buyer's name and email. Treat them as personal data: store only what your tool needs, and delete it when the seller disconnects you. See what leaves your machine for how we describe this to sellers.