Skip to main content
A Guidebook collects everything an organization knows about a single physical thing: a drawing, an assembly, a piece of equipment. It gathers the procedures that apply to it, the technical documentation for it, and its CAD or digital-twin model. A guidebook does not own procedures. It links them, so the same procedure can appear in any number of guidebooks and still have one place where its content lives.

Key fields

Linked procedures

Each link carries how it got there and how it is presented:

Extracting a procedure from a document

A reference document can become a draft procedure. POST /guidebooks/{guidebookId}/reference-material/{fileId}/extract-procedure reads the document and produces a procedure with steps, callouts, and outline structure, linked back with provenance: extracted. Converting a document first, with /convert, gives the structured form the extraction reads.

Endpoints

Full endpoint reference is available in the OpenAPI spec. Key operations:
  • GET /guidebooks: list guidebooks
  • POST /guidebooks: create one
  • GET /guidebooks/{guidebookId}: get a guidebook with its links
  • PATCH /guidebooks/{guidebookId}: update its fields
  • POST /guidebooks/{guidebookId}/procedures: link a procedure
  • PATCH /guidebooks/{guidebookId}/procedures/{procedureId}: pin, hide, or reorder a link
  • POST /guidebooks/{guidebookId}/tracked-objects: link an object for tracking
  • POST /guidebooks/{guidebookId}/reference-material/upload-url: upload documentation