Printer Status Callback

Last updated：2026-10-14 11:13:23

Source: ColorPark Open Platform documentation — Category: Interface – LAN Terminal (TCP); Article: Printer Status Callback (打印机状态回调); id=157, cate_id=113. Published / Updated: 2026-09-22 15:55:42

The Printer Status Callback Event pushes the printer's status information to the third-party platform in real time, so the third party can resolve issues promptly and avoid disrupting the order-printing flow.

Note: When a fault or stopped state occurs, the printer will not print orders. If a fault occurs, inspect the specific content of the fault callback event.

Interface Information

Parameter Value Description
IP 192.168.127.11 Use the corresponding IP within the LAN
Port 63333 Fixed port
Connection TCP Uses a TCP long connection
Encoding UTF-8 All sent and received data use UTF-8 encoding
Data format JSON Both sending and receiving use JSON format

Callback Example

{"event":"04","code":"0","status":"2","msg":"printing","notice_time":"2022-07-19 17:08:30"}

Return Result

Parameter Example Type Description
event 04 string 04 = printer status callback event (initiated proactively by the server)
code 0 string Result status code: 0 on success, 1 on failure
status 2 string Printer status: 0 offline · 1 normal · 2 busy · 3 fault · 4 stopped
msg printing string Displays different information per printer status: 0 offline · 1 normal · 2 busy · 3 fault · 4 stopped
notice_time 2022-07-19 17:08:30 string Notification time

Note — distinct status enum: This interface's status describes the printer device (offline / normal / busy / fault / stopped). Do not confuse it with the print-task status enum in the Print Task Status Callback (id=156): 0 preparing · 1 printing · 2 completed · 3 cancelled · 4 fault · 5 dispensing complete. The two enums share the number 3 = fault but otherwise differ; keep them separate when handling callbacks.

Minor observation: The callback example uses msg = "printing" for status = 2, whereas the field description lists the status-2 label as "busy" (忙碌). Both denote an occupied / working printer, so the difference is cosmetic rather than contradictory.

If the device encounters an unsolvable problem during debugging, you can contact the cloud-printing responsible person to troubleshoot and find a solution. Contact details:

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