Printago API
GET /v1/sequences/{id}/issuances

List issued serials for a sequence

The issued-serials ledger for a sequence, newest first. Each entry links the serial to the part build and print job that consumed it.

Requires: sequence.view

Path Parameters

id required
string
Sequence ID

Query Parameters

limit optional
number
offset optional
number

Response Schema

SequenceIssuance[]
Array of SequenceIssuance, each with:
createdAtrequired
string
format: date-time
idrequired
string
pattern: ^[a-z0-9]{24}$
orderIdrequirednullable
string
pattern: ^[a-z0-9]{24}$
orderItemIdrequirednullable
string
pattern: ^[a-z0-9]{24}$
parameterNamerequirednullable
string
partBuildIdrequirednullable
string
pattern: ^[a-z0-9]{24}$
printJobIdrequirednullable
string
pattern: ^[a-z0-9]{24}$
sequenceIdrequired
string
pattern: ^[a-z0-9]{24}$
serialrequired
string
skuIdrequirednullable
string
pattern: ^[a-z0-9]{24}$
storeIdrequired
string
pattern: ^[a-z0-9]{24}$
targetoptional
object
The physical item a serial was allocated for, recorded so queue and history views can explain which item received which number. A plate-aware share-mode stamp carries only the plate (the value applies to every matching occurrence there); an increment-mode stamp pins the exact object instance in the 3MF's stable `(object_id, instance_id)` identity.
identifyIdoptional
string
instanceIdoptional
number
objectIdoptional
string
plateIdoptional
number
updatedAtrequired
string
format: date-time
valuerequired
number

Example Response

200 OK — application/json 
[
  {
    "sequenceId": "string",
    "value": 1,
    "serial": "string",
    "parameterName": "string",
    "partBuildId": "string",
    "printJobId": "string",
    "skuId": "string",
    "orderId": "string",
    "orderItemId": "string",
    "target": {
      "plateId": 1,
      "objectId": "string",
      "instanceId": 1,
      "identifyId": "string"
    },
    "id": "string",
    "storeId": "string",
    "createdAt": "2025-01-15T12:00:00.000Z",
    "updatedAt": "2025-01-15T12:00:00.000Z"
  }
]