POST /nesting/geometry.
When to use the importer
- Your files carry layers that need mapping (e.g. an “ENGRAVE” layer vs. the cut path).
- You want a human (or your UI) to review import results before nesting.
- You’re building an interactive import experience in your product.
POST /nesting instead.
Session lifecycle
Create a session
POST /importer/Session (CreateImportSession) with your ImportSessionSettings.
Returns a session identity used by every subsequent call.Add files
POST /importer/File (CreateFileSettings) to add each file to the session. Update a
file’s settings with PUT /importer/File, or remove it with DELETE /importer/File.Review layers & assignments
GET /importer/Assignments (GetAssignmentTypes) lists the assignment types a layer can
be given. Apply assignments through the file/model settings so the importer knows which
layers are cut paths, which are engraving, and which to ignore.Inspect the model
GET /importer/Model (RetrieveModelIdentity) returns the interpreted model;
PUT /importer/Model (UpdateModelSettings) adjusts model-level settings.Retrieve results
GET /importer/Result (RetrieveResultIdentity) returns the imported geometry, ready to
nest via POST /nesting/geometry.Keeping a session alive
Long interactive sessions can be kept warm withKeepSessionAlive so they aren’t reclaimed
mid-edit. Complete or cancel sessions you’re done with rather than leaving them to expire.
Endpoint summary
| Endpoint | Method | Purpose |
|---|---|---|
/importer/Session | POST | Create a session |
/importer/Session | DELETE | Cancel session settings |
/importer/Session/Cancel | DELETE | Cancel the session |
/importer/Session/Complete | PUT | Complete the session |
/importer/File | POST / PUT / DELETE | Add / update / remove a file |
/importer/Model | GET / PUT | Retrieve / update the model |
/importer/Result | GET | Retrieve imported geometry |
/importer/Assignments | GET | List layer assignment types |
Next
Nest the imported geometry
Feed the retrieved geometry to
POST /nesting/geometry.