Get Print Job Status

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.

Polls the current status of a print job by its ID.
Use as an alternative or complement to webhookUrl when your POS
cannot receive inbound connections.

Polling strategy: Poll every 2–3 seconds. Stop when status is
COMPLETED 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 (not GET as in Local mode) due to cloud relay
routing requirements, and print_job_id travels in the request body — not as a query
parameter.

Like every other Cloud endpoint, this one requires the signed Authorization and timestamp
headers.

Request

Path Params

Header Params

Body Params application/jsonRequired

Examples

Responses

🟢200OK

application/json

Print job status returned.

Bodyapplication/json

🟠400Bad Request

🟠404Record Not Found

🔴500Server Error

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://api-uat.kushkipagos.com/terminal/v1/SN71652/sync/print_job' \
--header 'Authorization: nRvpFJZHjqLU4k8Rz2YiDvxA3mQs9oB1cW7eT0=' \
--header 'timestamp: 1700000000000' \
--header 'Content-Type: application/json' \
--data '{
    "print_job_id": "CUST-TICKET-001"
}'

Response Example

200 - Job completed

{
    "printJobId": "CUST-TICKET-001",
    "status": "COMPLETED"
}

Modified at 2026-08-20 21:30:31

Create Print Job

Local Services

Get Print Job Status

🚧 Beta — Early Access#

Request

Responses

🚧 Beta — Early Access