---
title: "User terminal config assignment"
method: PUT
path: "/public/v2/user-terminals/configs/assign"
tags: ["User Terminals"]
---

# User terminal config assignment

`PUT /public/v2/user-terminals/configs/assign`

Required permission: Device configuration assignment, Edit.<br/>Assign the config (or none) to the user terminals. For each terminal if it is currently online, the config will immediately be sent. Else, the config will be sent when it comes online. On error no assignment occurs. Currently terminal configIds are only visible on starlink website.

## Request body

- AssignUserTerminalsConfigRequest
  - `configId` string, nullable — Config id (or none) to assign to user terminals
  - `userTerminalIds` string[], required — UserTerminalIds to immediately update

## Response `200`

Success

- ServiceResponse
  - `errors` ValidationResult[], nullable
    - `memberNames` string[], nullable
    - `errorMessage` string, nullable
  - `warnings` ValidationResult[], nullable
    - `memberNames` string[], nullable
    - `errorMessage` string, nullable
  - `information` string[], nullable
  - `isValid` boolean

## Other responses

- `400` — Bad request. Invalid or missing parameter
- `401` — Unauthorized
- `403` — Forbidden, either you don't have access to the account or a terminal or config is not on the account.
- `422` — Unprocessable Content

---

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