Get Print Job Status

Testing

https://api-uat.kushkipagos.com

GET

/terminal/v1/print_job

Returns the current status of a print job by its ID.

🚧 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 this as an alternative or complement to webhookUrl when your POS cannot receive
inbound connections from the terminal.

Polling strategy: Poll every 2–3 seconds. Stop when status is COMPLETED or FAILED.

`status`	Description
`PENDING`	Job is queued, waiting to be processed.
`IN_PROGRESS`	The driver is sending commands to the printer.
`COMPLETED`	Ticket printed and cut successfully.
`FAILED`	Hardware error occurred. See `errorCode`.

In Local mode this endpoint is a GET with print_job_id as a query parameter. The Cloud
variant uses POST with the ID in the body — do not copy one integration onto the other.

Like every other endpoint, it requires the signed Authorization and timestamp headers.

Request

Query Params

Header Params

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 '/terminal/v1/print_job?print_job_id=RECEIPT-20240317-001' \
--header 'Authorization: nRvpFJZHjqLU4k8Rz2YiDvxA3mQs9oB1cW7eT0=' \
--header 'timestamp: 1700000000000'

Response Example

200 - Job completed

{
    "printJobId": "RECEIPT-20240317-001",
    "status": "COMPLETED",
    "externalReference": "Order-4421"
}

Modified at 2026-08-31 16:19:35

Create Print Job

Print Job Webhook (inbound — implemented by your POS)

Get Print Job Status

🚧 Beta — Early Access#

Request

Responses

🚧 Beta — Early Access