Sign an allowed QZ print request
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.
Requires a browser session with labels.read. Only recent printer-discovery requests and bounded, single-copy raw PT-P710BT jobs are accepted. Cross-site, file, network, serial and direct USB commands are rejected. Private keys remain on the server.
adminSessionauthjs.session-token<token>Authenticated Auth.js browser session cookie; each operation declares its required permission. Not restricted to administrators. HTTPS deployments use the secure-prefixed cookie variant.
X-Organization-ID?stringOrganization membership selected for this request. User-bound credentials may select any active membership; standalone tokens may only repeat their pinned organization ID.
uuidapplication/json- body
request*stringExact serialized QZ request string.
Base64 RSA SHA-512 signature.
response?stringtext/plaincurl -X POST 'https://inventory.example.com/api/v1/labels/qz-sign' \ -H 'Content-Type: application/json' \ -d '{ "request": "string"}'"string"Read the optional QZ signing certificate GET
Requires a browser session with labels.read. Without signing configuration the application uses QZ approval prompts.
List reusable label setups GET
Requires labels.read (read scope for standalone tokens). Setups are ordered by name and contain the complete print layout.