API concepts
Statuses and next steps
Every job status and the hint that comes with it.
A job moves through these statuses. The next field tells your system what to do at each one.
| submitted | estimate_pending. Momentary; the estimate is being computed. |
|---|---|
| estimated | accept. Or awaiting_staff_quote once you accepted above your limit. |
| quoted | accept. Glyph confirmed the price. |
| invoiced | pay. The invoice is at invoice.url. |
| paid | awaiting_release. A person at Glyph releases it to the queue. |
| queued | scheduled. In the shop queue. |
| scheduled | scheduled. schedule.start and schedule.end are set. |
| running | in_production. |
| done | awaiting_shipment. |
| shipped | complete. |
| cancelled, declined | The job stopped. Contact us. |
Operation status
Each operation under a job has its own status: pending, running, or done, with scheduled_machine, scheduled_start, and scheduled_end once planned.
Order and product status
On-demand orders and products have their own sets. See Orders and Products and variants.
Inquiry status
Inquiries use a separate set: submitted, under_review, accepted, declined, queued, in_production, delivered, complete, archived. An inquiry that becomes a job carries a job object with the job's own status.