---
title: "Assign a terminal to a sub account"
method: POST
path: "/v1/terminals/assign/{subAccountId}"
tags: ["Terminals"]
---

# Assign a terminal to a sub account

`POST /v1/terminals/assign/{subAccountId}`

You can use this endpoint to assign a terminal to an sub account.

## Path parameters

- `subAccountId` string, required

## Headers

- `accountId` string, uuid, required

## Request body

- TerminalAssignmentRequest
  - `serialNumber` string, required — Serial number
  - `terminalLabel` string — Terminal label

## Response `200`

OK - your request was successful.

- object
  - `code` string, required — Response Code
  - `description` string, required — Response description
  - `data` TerminalResult, required
    - `terminalId` string, required — Terminal ID
    - `serialNumber` string, required — Serial number
    - `accountId` string, required — Account ID
    - `parentAccountId` string, required — Parent account ID
    - `merchantName` string, required — Merchant name
    - `terminalLabel` string, required — Terminal label
    - `createdAt` string, date-time, required — Creation timestamp
    - `updatedAt` string, date-time, required — Updated timestamp

## Other responses

- `400` — The request body sent by merchant did not pass the validation checks
- `401` — The access_token provided to access the resource is missing or invalid.
- `403` — The client does not have the permissions to access this resource
- `404` — The record that the client is trying to access does not exist.
- `429` — The client has maxed out the number of calls within a time period on this resource.
- `500` — Downstream system error.

---

[API](https://skmtc.net/nomba/apis/vendor-api.md) · [All operations](https://skmtc.net/nomba/apis/vendor-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/nomba/vendor-api/revisions/41727ac9be5f/schema)