---
title: "Assign terminals"
method: POST
path: "/assignTerminals"
tags: ["General"]
---

# Assign terminals

`POST /assignTerminals`

Assigns one or more payment terminals to a merchant account or a store. You can also use this endpoint to reassign terminals between merchant accounts or stores, and to unassign a terminal and return it to company inventory.

## Request body

- AssignTerminalsRequest
  - `companyAccount` string, required — Your company account. To return terminals to the company inventory, specify only this parameter and the `terminals`.
  - `merchantAccount` string — Name of the merchant account. Specify this parameter to assign terminals to this merchant account or to a store under this merchant account.
  - `merchantInventory` boolean — Boolean that indicates if you are assigning the terminals to the merchant inventory. Do not use when assigning terminals to a store. Required when assigning the terminal to a merchant account. - Set this to **true** to assign the terminals to the merchant inventory. This also means that the terminals cannot be boarded. - Set this to **false** to assign the terminals to the merchant account as in-store terminals. This makes the terminals ready to be boarded and to process payments through the specified merchant account.
  - `store` string — The store code of the store that you want to assign the terminals to.
  - `terminals` string[], required — Array containing a list of terminal IDs that you want to assign or reassign to the merchant account or store, or that you want to return to the company inventory. For example, `["V400m-324689776","P400Plus-329127412"]`.

## Response `200`

OK - the request has succeeded.

- AssignTerminalsResponse
  - `results` object, required — Array that returns a list of the terminals, and for each terminal the result of assigning it to an account or store. The results can be: - `Done`: The terminal has been assigned. - `AssignmentScheduled`: The terminal will be assigned asynschronously. - `RemoveConfigScheduled`: The terminal was previously assigned and boarded. Wait for the terminal to synchronize with the Adyen platform. For more information, refer to [Reassigning boarded terminals](https://docs.adyen.com/point-of-sale/managing-terminals/assign-terminals#reassign-boarded-terminals). - `Error`: There was an error when assigning the terminal.

## Other responses

- `400` — Bad Request - a problem reading or understanding the request.
- `401` — Unauthorized - authentication required.
- `403` — Forbidden - insufficient permissions to process the request.
- `422` — Unprocessable Entity - a request validation error.
- `500` — Internal Server Error - the server could not process the request.

---

[API](https://skmtc.net/adyen/apis/tfmapiservice.md) · [All operations](https://skmtc.net/adyen/apis/tfmapiservice/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/adyen/tfmapiservice/versions/4c0e71faa937/schema)