Get Print Job Status
Testing
UAT Testing Env
https://api-uat.kushkipagos.com
UAT Testing Env
https://api-uat.kushkipagos.com
POST
/terminal/v1/{terminalSerial}/sync/print_job
🚧 Beta — Early Access
This API is in early access. Endpoints, parameters, and response structures
may change without prior notice. Do not deploy to production without
coordinating with the Kushki integration team.
Use as an alternative or complement to
webhookUrl when your POScannot receive inbound connections.
status isCOMPLETED or FAILED.status | Description |
|---|---|
PENDING | Job is queued, waiting to be processed. |
COMPLETED | Ticket printed and cut successfully. |
FAILED | Hardware error occurred. See errorCode. |
In Cloud mode this endpoint uses POST(notGETas in Local mode) due to cloud relay
routing requirements, andprint_job_idtravels in the request body — not as a query
parameter.
Authorization and timestampheaders.
What you encrypt
{
"print_job_id": "CUST-TICKET-001"
}Request
Path Params
Header Params
Body Params application/jsonRequired
Responses
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://api-uat.kushkipagos.com/terminal/v1/SN71652/sync/print_job' \
--header 'Authorization: Basic 9f2c4e1b7a63d8f05c2e9b41a7d3086fbe15c4d29a7e0b38f6c1d52a94e7b3c0' \
--header 'timestamp: 1748476800' \
--header 'Content-Type: application/json' \
--data '{
"data": "a3f14c7e9b02d85fbc1e46a9d370f28b:9e0d7f21c4a8b653e17d902fac48b5d6e83c1704a9f26db8"
}'Response Response Example
200 - Job completed
{
"printJobId": "CUST-TICKET-001",
"status": "COMPLETED"
}Modified at 2026-09-09 17:59:59