Acknowledge a printer claim
The API runs on your application instance. Schemas and field names come directly from the OpenAPI specification. Session-authenticated requests require a session on that instance.
Agent only. Report submitted after Windows accepts the RAW job, failed after a definite failure, or uncertain if acceptance is ambiguous. The receipt clears the stored payload. It does not prove physical printing.
printAgentAuthorizationBearer <iprt_ token>Dedicated printer credential issued once by POST /label-printers. Only valid for agent claim and acknowledgement.
application/json- body
id*stringuuidclaimId*stringuuidstatus*string"submitted""failed""uncertain"spoolJobId?|nullReceipt recorded.
application/json- response
ok*booleancurl -X POST 'https://inventory.example.com/api/v1/label-print-agent/ack' \ -H 'Content-Type: application/json' \ -d '{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "claimId": "88057929-7728-4a26-8396-f965dcc8b947", "status": "submitted"}'{ "ok": true}Create or pin a manual relationship POST
One endpoint must match the resource id in the path. Containment relationships reject invalid parents, self-reference, and direct or indirect cycles. Creating an existing spatial relationship converts it to a manual relationship.
Claim the next job for a printer POST
Windows agent endpoint; use the dedicated iprt_ credential, not an inventory API token. Reuse claimId to recover the same claim. Stale claims become uncertain after five minutes and are never handed out again. History cleanup runs on polling after seven days.