slicing

Report one slice outcome

SLICE_SERVICE_SECRET bearer, called once per job with ready, failed, or manual. Idempotent from the caller's side - a duplicate POST just overwrites the same fields, which is harmless because these are not a lifecycle transition. The mass fields are validated hard: filament_g: 0 is REJECTED outright, because zero grams is a broken slicer resolution and never a measurement, and accepting it would put a $0.00 material line on a quote with the provenance of a real slice. gcode_file_id is optional - a member's own pre-sliced upload reports ready with no file payload.

post/api/prints/slicing/result

Request

  • Base URL: https://www.immersivecommons.com
  • URL: https://www.immersivecommons.com/api/prints/slicing/result
  • Auth: HTTP bearer

Request body

request_idstring required
slice_status'ready' | 'failed' | 'manual' required
gcode_file_idstring

Optional. Omitted for a member's own pre-sliced upload, whose file is already in the vault.

Response

The stored slice status.

okboolean required
request_idstring required
slice_statusstring required

Changes

No recorded changes to this operation across all 1 revision of this API.