Skip to main content
Terminal operations let you send administrative commands to a registered payment terminal and read the results. Use them to run an end-of-day close, ask the terminal to upload its logs, check for software updates, or open the terminal menu, without physically touching the device. Operations are asynchronous. You send a command, the API dispatches it to the terminal and returns immediately with a PENDING operation, and the terminal processes the command in the background. You then poll the operation to see how it finished.
Terminal operations are administrative commands. They do not start a payment. To take a payment on a terminal, see creating a terminal session.

Available operations

Send a command

The request body identifies the terminal and the operation to run.
The response is returned as soon as the command is dispatched to the terminal. The terminal’s response is processed asynchronously, so the operation starts with status PENDING.
See POST /admin/terminals/operations for the full schema.

Idempotency

Pass an Idempotency-Key header to ensure the same command is only executed once, for example when retrying after a network error.

One operation at a time

A terminal processes one operation at a time. If an operation is already pending for the terminal, the API responds with 409 Conflict and a Retry-After header indicating how many seconds to wait before retrying.

List operation results

Poll operations to see how a command finished. The endpoint returns operations and supports filtering by terminal_id and operation_id.
To check a single operation, filter by the id returned when you sent the command.
See GET /admin/terminals/operations for the full schema.

Operation status

Scopes

Last modified on July 9, 2026