The two calls in this folder answer the questions you need before you debug a payment: can I reach the terminal at all, and which build is it running. Neither one moves money, so you can call them as often as you like.Kushki ONE Cloud is currently in Beta for Perú 🇵🇪. Do not deploy to production without coordinating with the Kushki integration team.
Operations#
| Operation | Endpoint | What it tells you |
|---|
| Connection test | POST /terminal/v1/{terminalSerial}/sync/local/test | Checks that your POS reaches the terminal. Moves no money. |
| Terminal info | POST /terminal/v1/{terminalSerial}/sync/config/terminal_info | Returns {model, room, serialNumber}. room is the app version running on the terminal. |
When to use them#
Run Connection test first. It validates network, port and credentials in a single call, which means a failure here rules out three causes at once:A TER-002 means the terminal is not responding — check connectivity and that the port is open.
An authentication error means the signature is wrong, not the network.
Terminal info is how you confirm which terminal you are talking to, and which app version it runs. Include the room value in any report you send to support: it is the only way to tell which build produced a given behaviour.