Print Job Webhook (inbound — implemented by your POS)

Testing

UAT Testing Env

https://api-uat.kushkipagos.com

POST

/terminal/v1/print/webhook

Implemented by your POS system
This endpoint lives in your infrastructure, not in Kushki ONE.
When a print job completes or fails, the terminal POSTs to the webhookUrl
you supplied in the print job request.
It is documented here so your team knows the expected payload shape.

Your webhook endpoint must return HTTP 2xx. Print-job delivery is
fire-and-forget: unlike the transaction events webhook, it is not retried.
If the callback does not arrive within ~60 seconds, fall back to
GET /terminal/v1/print_job?print_job_id={id}.

Do not use this as your only signal for a payment receipt. A lost webhook and a failed print
look identical from your side — poll to confirm.

Request

Body Params application/jsonRequired

Examples

Responses

🟢200OK

Webhook received.

This response does not have a body.

Request Example

Shell

JavaScript

Java

Swift

cURL

Job completed successfullyJob failed — cover open

curl --location 'https://api-uat.kushkipagos.com/terminal/v1/print/webhook' \
--header 'Content-Type: application/json' \
--data '{
    "printJobId": "RECEIPT-20240317-001",
    "status": "COMPLETED",
    "externalReference": "Order-4421"
}'

Response Example

{}

Modified at 2026-10-07 15:31:32

Get Print Job Status

Diagnostics

Print Job Webhook (inbound — implemented by your POS)

Implemented by your POS system#

Request

Responses

Implemented by your POS system