The response isn't the same as the POST terminal/charge, or POST terminal/charge/queue or the GET transaction/{id} route.

The response is the terminal data.

**Please be aware that this call queries the terminal directly, which will cause the terminal to be busy for several seconds, and will not work correctly if the terminal is already busy. **

If you are polling for transaction data, it's recommended to use the GET transaction/{id} route instead. This route lets you get data straight from the terminal, just in case you need to. If an invalid transaction ID is given, the response will be a 422. If the transaction exists in our API but not in the device's batch, the response is 200.

If the device is busy, the response is a 200. If the device isn't busy and the transaction is found in the batch, you will get a 200, and the response will be the first 200.