Print Task Callback

Last updated:2026-10-13 13:54:08

Receive print updatesProvide a callback endpoint in your system to receive completion and error updates.

What do I need before starting?

Prepare a connected printer, its ID and key, an accessible image URL and physical print dimensions. Keep the key on your server.

Submission is not completion. Save the returned task ID. Call Start Print only when the device requires a second confirmation.

Receive print results — Provide a callback URL in your system to receive completion or exception notifications.

What do you need to prepare before starting?

Prepare an onboarded device, the device ID and secret key, an accessible image URL, and the actual print dimensions. Keep the secret key on the server side; do not embed it in a web page.

Submitting successfully does not mean printing is finished. Save the returned task ID; only when a device is set to secondary confirmation do you need to call "Start Printing" again.

Third parties must configure a custom callback URL on the open platform (e.g., http://XXXX.com/api/callback). When a print task's status is updated, the open platform will push the task information to that address in real time via POST, enabling the third party to automate order-status handling (e.g., shipping, refunds, alerts, inventory processing).

Callback URL

Item Value
Interface URL http://XXXX.com/api/callback (custom-defined by the third party)

Callback Result

Parameter Data Type Sample Value Description
type string printing Callback event type: printing — printing in progress; finish — finished; cancel — canceled; imageStatus: image status; pause — printing paused; failure: print failure / engraving failure
taskid string 20000196 Unique ID assigned to the print task
printer_id string 500001 Printer ID assigned for the print job
once string 8305 Random value sent with each request
time string 1646790335 Timestamp sent with each request
sign string 9ce3ce7a3fccaf3d7715bd7e9bb1dc1c Signature
order_id string 8003A Order number in the partner's system. If two orders are merged for printing, the two order numbers are separated by a comma, e.g. 1569885222,1785336685
status string 1 Print task status: 1 printing in progress; 2 print finished; 3 print canceled; 4 print fault; 5 feed failure; 6 output failure; 7 homing failure; 8 printer not reset; 11 insufficient stock (order cannot be printed, backend must refund); 12 stock warning (stock is 0, the next order will have insufficient stock and cannot be printed); 13 printing paused; 14 print failure
receive_status string 1 Client image-receiving status: 0 pending; 1 received successfully; 2 receive failed
msg string Print finished Displays different information based on task status. 1: printing in progress; 2: print finished; 3: print canceled; 4: print fault

If a problem that cannot be resolved occurs during device commissioning, contact the cloud-printing responsible person for troubleshooting. Contact details: Phone: 137-5177-4454 (WeChat same number) Email: info@ColorPark.cn

UV cloud-printing service provider with deep hardware–software integration ® Ruifengcai