---
title: "Replace a screen's device"
method: POST
path: "/v1/screens/{id}/claim-replacement"
tags: ["screens"]
---

# Replace a screen's device

`POST /v1/screens/{id}/claim-replacement`

## Request

- Base URL: `https://api.brixsignage.com`
- URL: `https://api.brixsignage.com/v1/screens/{id}/claim-replacement`
- Auth: HTTP bearer

Bind a new device, identified by the 6-digit pairing code it is displaying, to an existing screen. The screen keeps its identity, assigned content, and history. This endpoint is rate-limited because the pairing code is a small, guessable value.

## Path parameters

- `id` string, required

## Request body

- object
  - `code` string, required: The 6-digit code the new device shows.

## Response `200`

Success.

- object
  - `data` object, required
    - `id` string, required
    - `paired` true, required

## Other responses

- `401`: Missing, expired or revoked bearer token.
- `403`: The token lacks the permission this operation needs (see `x-brix-permission`).
- `404`: No screen with this id, or no device shows that code.
- `409`: `ambiguous_code` (two devices show it) or `already_claimed`.
- `410`: The code has expired.
- `422`: `code` is missing.
- `429`: Too many wrong codes; wait and try again.
- `5XX`: Server error. The body carries a `requestId` to quote to support.

---

[API](https://skmtc.dev/brixsignage/apis/brix-api.md) · [All operations](https://skmtc.dev/brixsignage/apis/brix-api/llms.txt) · [OpenAPI document](https://skmtc.dev/brixsignage/apis/brix-api/revisions/02fd3665dc7d?raw)