---
title: "Create a request to associate a Wearable Device"
method: POST
path: "/shop/terminal-requests/associate-wearable"
tags: ["TerminalRequests"]
---

# Create a request to associate a Wearable Device

`POST /shop/terminal-requests/associate-wearable`

This endpoint sends a request to the terminal to associate a wearable device.

## Request body

- object
  - `terminal_id` string, object-id, required — Identifier of the physical terminal that should prompt for the wearable tap. Must be a terminal registered to the caller's site; the terminal scans the wearable and completes the link to `customer_id`.
  - `customer_id` string, uuid, required — Identifier of the customer that the scanned wearable should be linked to. Once associated, the wearable can be used as a payment device for this customer's stays and visits.
  - `order_id` string, object-id, nullable — Optional identifier of an order to attach the wearable to at association time, useful for express check-in flows. Pass `null` to leave the wearable unattached.

## Response `200`

The Terminal Request was successfully retrieved

- object
  - `data` TerminalRequest, required
    - `id` string, object-id, required — The ID of the request.
    - `site_id` string, uuid, required — The ID of the site the request is associated with.
    - `terminal_id` string, required — The serial number of the terminal associated with the request.
    - `service_id` string, required — The ID of the service the request is associated with.
    - `status` 'pending' | 'succeeded' | 'failed', required — The status of the request.
    - `amount` integer, nullable, required — The amount being sent to the terminal in the request.
    - `succeeded_at` string, date-time, nullable, required — The date and time the request was successfully completed.
    - `failed_at` string, date-time, nullable, required — The date and time the request failed.
    - `processor_data` object, required — An object of key-value pairs containing the response from the terminal operation.

## Other responses

- `400` — The request failed.
- `401` — The user is unauthenticated
- `403` — The authenticated user does not have permission.
- `422` — The request didn't pass validation

---

[API](https://skmtc.dev/try/apis/trybe-api.md) · [All operations](https://skmtc.dev/try/apis/trybe-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/try/trybe-api/revisions/f37f92702da5/schema)