API reference
Every endpoint, with the scope it needs and how often it may be called. The field tables on each page are generated from the same schemas the server validates against.
Base URL
https://lucentimaging.com.au/api/print/v1Endpoints
| Endpoint | Scope | Limit | Purpose |
|---|---|---|---|
GET /catalogue | price:read | 120/min | Products and material ids a line may reference |
GET /orders | orders:read | 120/min | List this account's orders, newest first |
POST /orders | orders:write | 30/min | Turn a held quote into a job |
GET /orders/{id} | orders:read | 120/min | Status, totals, lines and tracking |
POST /orders/{id}/cancel | orders:write | 30/min | Cancel an order that has not been made yet |
POST /quotes | price:read | 60/min | Price a basket and hold the price for 24h |
GET /quotes/{id} | price:read | 120/min | Read a quote back |
POST /uploads | orders:write | 60/min | Presign an S3 PUT for artwork |
Reading these pages
Field tables are generated from the API's own validation schemas, so what is listed is exactly what the server accepts and returns - including every length, minimum and maximum. Where a bound alone does not explain a field, there is a note beside it.
Response tables describe the contents of data. The envelope around it is always { data, error }, and list endpoints add nextCursor beside them.