Reboot
Overview
The reboot command allows you to restart the terminal. This can be useful if the terminal seems to be running slow or if it has stopped responded. If you want to force a reboot, set the "force" value to "true". This will restart the terminal regardless of whether it is currently processing a transaction or unresponsive.
NOTE
This is only available for the Direct and App-to-app Integration methods and not for Cloud.
List of coding scenarios that use this endpoint:
Request Structure
| Element | Type | Description | Size | Required |
|---|---|---|---|---|
| apiVersion | String | API version number | V20 | Required |
| istConfigCode | String | Moneris provided integration configuration code | V50 | Required |
| dataId | String | Merchant defined unique identifier for the data object | V50 | Required |
| dataTimestamp | String | Date and time of the request (YYYY-MM-DD HH:MM:SS) | F19 | Required |
| data | Object | Object that contains all transaction requests | — | — |
| request | Array | Contains data applicable to transaction request | — | — |
| terminalId | String | Destination Terminal ID | F8 | Optional |
| action | String | "cancel" | V50 | Required |
| force | String | If value is set to "true", terminal will perform a forced reboot. Warning: Forced reboot will restart the terminal regardless of its current state. Therefore, if the terminal is in the middle of a transaction and a forced reboot command is issued, the terminal will reboot mid transaction. | V4 | Optional |
Request example
{
"apiVersion": "3.0",
"istConfigCode": "example_istConfigCode",
"dataId": "example_dataId",
"dataTimestamp": "1969-12-31 23:59:59",
"data": {
"request": [
{
"terminalId": "example_terminalId",
"action": "reboot"
}
]
}
}Response Structure
| Element | Type | Description | Size | Required |
|---|---|---|---|---|
| apiVersion | String | API version number | V20 | Required |
| statusCode | String | Status code for the overall transaction request | V4 | Required |
| status | String | Description of the statusCode | V50 | Required |
| dataId | String | Merchant defined unique identifier for the data object | V50 | Required |
| dataTimestamp | String | Date and time of the request (YYYY-MM-DD HH:MM:SS) | F19 | Required |
| data | Object | Object that contains all transaction requests | — | — |
| response | Array | Contains data applicable to transaction request | — | — |
| action | String | "cancel" | V50 | Required |
| statusCode | String | Status code for individual request | V4 | Required |
| status | String | Description of the individual statusCode | V50 | Required |
| completed | String | "true" or "false" | V5 | Required |
| terminalId | String | Destination Terminal ID | F8 | Optional |
Response example
{
"apiVersion": "3.0",
"statusCode": "example_statusCode",
"status": "example_status",
"dataId": "example_dataId",
"dataTimestamp": "1969-12-31 23:59:59",
"data": {
"response": [
{
"statusCode": "example_statusCode",
"status": "example_status",
"completed": "true",
"action": "reboot"
}
]
}
}Errors
If your response contains errors, visit the Errors page for a detailed description of each one.

