Check Device Information for a Square Terminal

Applies to: Terminal API

Learn how to check device information for a Square Terminal using the Terminal API.

Link to section


After pairing a Square Terminal and a POS application, use the Terminal API to check the real-time device information of one or more remote devices. This feature uses the TerminalAction object and the PING Terminal action type. When you need to remotely monitor the performance of a group of Square Terminal devices, use the PING Terminal action to capture information such as network connectivity, battery level, and device OS version.

Link to section

Requirements and limitations

  • A Square Terminal must be paired with a POS application.
  • Applications must have the following OAuth permissions:
    • PAYMENTS_READ for getting or searching for a Terminal action request.
    • PAYMENTS_WRITE for creating or canceling a Terminal action request.
  • Ensure that the Square Terminal software is up to date. On the Square Terminal, choose Settings, choose General, choose About Terminal, and then check the software version. For more information, see Square Terminal FAQ.
  • Your developer account must be enabled to subscribe to Terminal API action webhooks.
Link to section

When to check for device information

You might need to check the device information when:

  • A seller has a group of devices that aren't operated by anyone on the floor (automated operation).
  • You're not located at the same customer site as the seller (remote monitoring).
  • You need to regularly monitor network connections due to a recent server outage.

The TerminalAction object provides a foundational method for using the Terminal API to collect device information in real time and measure device availability. With the PING Terminal action, you send a request to the device and see whether a device is connected to your seller's network, as indicated by the device's status. If the device is online and sends a response back, you can get additional device status updates.

As a device monitoring and health status feature, you can periodically use the PING Terminal action so that your seller's devices maintain availability for buyers. The Terminal action request and response are limited to devices that are signed in with a Terminal API device code and that are paired with the Terminal API and your POS application.

Link to section

Set up the PING Terminal action

  1. Create a PING Terminal action request using the CreateTerminalAction endpoint that includes the PING action type and the device_id, which is found on the back of the Square Terminal device.

    Create terminal action

    You receive a Terminal action response that includes an ID and a PENDING action status.

    { "action": { "id": "termapia:vguubuhbiuhfyrfrugv", "device_id": "device_id123", "deadline_duration": "PT5M", "status": "PENDING", "created_at": "2021-07-28T23:22:07.476Z", "updated_at": "2021-07-28T23:22:07.476Z", "location_id": "LWTMJESMBQXZC9", "type": "PING", "app_id": "sq0ids-ESXCwyTF7NBxodprF_pvhA" } }
  1. After the Terminal device has acknowledged the request, the action status transitions from PENDING to COMPLETED and the action object updates with the device details in device_metadata.

  1. Using the from CreateActionResponse, create a GET request using the GetTerminalAction endpoint to retrieve the PING action.

    Get terminal action

    The PING Terminal action is in a PENDING state if the Square Terminal hasn't acknowledged the request, it's dealing with a slow Internet connection, it's turned off, or it's not signed in to the Terminal API application using a device code from the Devices API. In this case, subscribe to the terminal.action.created and terminal.action.updated webhooks. For more information, see Square Webhooks.

Link to section

Search for a PING Terminal action by status

You can also search for devices based on a specified status. When you send the POST request to the SearchTerminalActions endpoint, provide the status query in the request body. You can query by specifying PENDING, IN-PROGRESS, COMPLETED, or CANCELED for the status.

The following request example specifies the PING action type and a limit of 2 for the number of results returned from the request:

Search terminal actions

Link to section

Subscribe to events for Terminal action status updates

When a TerminalAction object is created or updated, webhook notifications are sent to the endpoint that is registered for a POS application. To get the notifications, be sure that your application is updated in the Developer Dashboard with the following webhooks:

  • terminal.action.created
  • terminal.action.updated

A full copy of the object is sent to your application at your webhook URL for every action status update, which includes PENDING, IN_PROGRESS, COMPLETED, or CANCELED.