Terminal API Quickstart

Applies to: Terminal API | Devices API | Locations API | OAuth API | Webhooks

Learn how to connect and set up a Square Terminal with the Terminal API.

Link to section


To connect a Square Terminal with a third-party POS application, complete the following steps:

  1. Create a new device code.
  2. Set up a Square Terminal.
  3. Pair a Square Terminal with a POS application.

After you pair a Square Terminal, set up Terminal API webhook notifications and an OAuth flow so that you get notified of Terminal API events and establish access tokens for making checkout requests. Completing these steps establishes the integration between the Square Terminal and the POS application. It also allows you to use the Terminal API to send and receive requests for payment checkouts and other processes.

After you establish the integration, see Take Payments with the Terminal API.

Link to section

Requirements and limitations

  • You've created a Square developer account and an application.

  • You've subscribed to webhook events.

  • You've create a new device code with the Devices API CreateDeviceCode endpoint.

  • Your Square developer account allows you to host applications that you can use with the Terminal API for a seller's in-person business. When you subscribe to webhook events, you receive notifications of Terminal API related activity that occurred.

Link to section

1. Create a new device code

Provide the following details in the device_code request body:

  • name - This is an optional property, but it's recommended to enter a name that identifies the system that the seller uses with the POS application and the Square Terminal.
  • product_type - Enter TERMINAL_API.
  • location_id - Enter the location ID that represents the seller's location.

Create device code

The response returns several fields, including:

  • The friendly name you used in the request.
  • The device pairing status, which is currently UNPAIRED.
  • The device code to enter in the Square Terminal.
  • The date and time on which the device code expires if not used.
{ id: "1234567890", name: "Counter 1", code: "AFZEFB", status: "UNPAIRED", location_id: "NHT...CGJ", product_type: "TERMINAL_API", pair_by: "1970-01-01 11:10", created_at: "1970-01-01 11:10", updated_at: "1970-01-01 11:10" }


If a location ID isn't set in the request, the location_id response value is the default location ID for the seller.

After a device code is created, the seller must use the device code to sign in to a Square Terminal within 5 minutes. If the device code isn't used within 5 minutes, the device code expires and you must request a new device code. After the initial sign-in, you can reuse the device code to sign in to the same Square Terminal for subsequent sign-in attempts.

After a seller signs in to a Square Terminal with the device code, the status changes to PAIRED and the device_id value of the Terminal device is available. The device ID is the serial number on the underside of the Square Terminal.

When the seller signs in, the POS application is notified through a webhooks event notification.

Did you know?

The Square Sandbox doesn't support the Devices API. If you're testing a Terminal API application in the Sandbox, use a Sandbox device ID that simulates a Square Terminal from the list of Sandbox test values for the Terminal API, instead of production device IDs obtained with the Devices API.

Link to section

2. Set up a Square Terminal

You must set up a new Square Terminal before use. If a previously used device is powered off, turn it on and check for software updates that might have been missed while the Square Terminal was powered off.

  1. Turn on the Square Terminal and connect it to your WiFi network.
  2. On the Square Terminal Sign in Page, choose Change Settings, choose General, and then choose About Terminal. If there are any pending software updates, update the Square Terminal to the latest version.
Link to section

Sign in to a Square Terminal

When a device code is available for the requested Square Terminal, a seller signs in to the Square Terminal using the following steps:

  1. On the Sign in Page, choose the Device Code button.

  2. Request a new device code by sending a POST request to v2/devices/codes.

  3. Display this code to the person performing the setup.

  4. Use the device code your application gathered.

    The Terminal screen should look like the following:

    A graphic showing a Square Terminal Ready screen.

Link to section

Sign out of a Square Terminal paired mode

If your Square Terminal is paired with a POS application, you might want to sign out of the Terminal. Signing out lets you pair the Square Terminal with a different POS application or use the Square Point of Sale application.

  1. Swipe from the left side of the screen to open the navigation drawer.
  2. Choose Settings.
  3. Choose Sign Out at the bottom of the menu.
Link to section

3. Pair a Square Terminal with a POS application

A seller might have more than one location where Square Terminals are used. In this case, when pairing a Square Terminal, the seller should pick the location of the Square Terminal to be paired. Otherwise, the default seller location is used. Before a POS application can use a Square Terminal to check out a buyer, the POS application must be paired to a Square Terminal at either the chosen location or the default location.


The Terminal API can only be used with device codes returned by the CreateDeviceCode endpoint. Other device codes, such as those created in the Seller Dashboard, aren't compatible with the Terminal API.

The pairing process involves the following steps:

  1. (Optional) The POS application uses the Locations API to present a location picker for the seller. If a location ID isn't set in the request, the default location is used.
  2. The POS application gets a device code from a CreateDeviceCode request.
  3. The seller enters the device code into the Square Terminal to sign in.
  4. The Square Terminal notifies Square that it's signed in using the device code.
  5. The POS application and Square Terminal are paired when the device code is used to sign in to the Terminal.
  6. The POS application receives a webhook showing that pairing is enabled and provides a device ID to be used in checkout requests for the paired Terminal.

The seller can log in to the Square Terminal multiple times with the same device code.

Link to section

Additional steps after pairing

After pairing the Square Terminal, set up webhook notifications and your OAuth flow.

Link to section

Webhook notifications for status updates

Square sends webhook notifications with each status update for a Square Terminal pairing request and for a Terminal API checkout request status update. If you add listening endpoints for these webhook notifications, you avoid polling a Square server to get the current status of either request. The application webhook endpoint should listen for the following notifications:

  • device.code.paired - Notifies of a pairing completion.
  • terminal.checkout.created - Acknowledges a new Terminal checkout.
  • terminal.checkout.updated - Notifies of a checkout status change.

The webhook payload for device.code.paired is an instance of DeviceCode with the current state of the object.

The webhook payload for the terminal.checkout notifications is an instance of the TerminalCheckout whose properties have changed as the connected Square Terminal processes the checkout.

Link to section

OAuth permissions for a Square Terminal

When you register the POS application with the Developer Dashboard, you get the access tokens needed to call Square APIs. For OAuth tokens, use the Developer Dashboard to test your OAuth flow in the Square Sandbox.

When you set up your OAuth flow, request the minimum permissions necessary to pair a Square Terminal and request a checkout. Doing so might increase adoption of the POS application and reduce your liability.

The following are the minimum permissions you need to request:


When sellers sign in to an integrated POS application, they should be redirected to a URL as shown in the following example:


The Square authorization page asks sellers to accept the POS application request for the following permissions:

  • Access to their Square Terminal credentials (DEVICE_CREDENTIAL_MANAGEMENT permission).
  • Access to their seller profile (MERCHANT_PROFILE_READ permission).
  • Read/write access to payments in their Square account (PAYMENTS_READ and PAYMENTS_WRITE permissions, respectively).

After the seller accepts the authorization request, the Square authorization page sends a GET response to the redirect URL that you specified for the POS application. For more information, see Receive Seller Authorization and Manage Seller OAuth Tokens.


If you're building an application for accounts other than your own, use the OAuth API to generate tokens for each of your customers. Each customer creates and uses their own device codes to put their Terminal into Connected Mode.

Link to section

Optional: Listen for the device pairing webhook

Validate the webhook notification for device.code.paired.

The following example shows the payload of the webhook:

Link to section

Optional: Request the pairing status

The Devices API returns the current status of a device pairing with a GET command, as shown in the following example:

Get device code

If the device code hasn't expired, a response similar to the following example is returned:

{ "device_code": { "id": "3YVR0WQ0VY6WG", "name": "Counter 2", "code": "QYXRJQ", "product_type": "TERMINAL_API", "location_id": "NHT82D0ENBCGJ", "pair_by": "2020-03-20T20:23:31.000Z", "created_at": "2020-03-20T20:18:31.000Z", "status": "UNPAIRED", "status_changed_at": "2020-03-20T20:18:31.000Z" } }

Check the status of the device code. If it isn't PAIRED, you need to request the device pairing again. Keep checking until the device is PAIRED. When paired, the POS client can send Terminal checkout requests.


Expired device codes aren't returned in ListDeviceCodes and GetDeviceCode operations.