---
title: "Claim multiple discovered devices"
method: POST
path: "/v1/screens/pending/claim"
tags: ["screens"]
---

# Claim multiple discovered devices

`POST /v1/screens/pending/claim`

## Request

- Base URL: `https://api.brixsignage.com`
- URL: `https://api.brixsignage.com/v1/screens/pending/claim`
- Auth: HTTP bearer

Claim multiple discovered devices as screens in one request, using `items`, an array of objects with `pairingId`, `name`, an optional `nodeId` and an optional `code`. Set `code` to the 6-digit code that the screen shows. If the code is wrong, the API does not claim that screen. Wrong codes count toward the same lockout as POST /v1/screens/claim. To claim a device from a different network using its 6-digit code, use POST /v1/screens/claim instead. This request is refused if your account is suspended or cancelled.

**Notes.**
- Items that are not pending on the caller's network are skipped, not refused; `claimed` lists the ones that became screens.
- One network can claim at most 100 devices an hour without a `code`. Items with the correct `code` are not limited.
- A request checks at most one wrong `code`. After a wrong code, the other items that have a `code` are skipped.
- The workspace owners get an email for each request that claims a device without a `code`.

## Request body

- object
  - `items` object[], required
    - `pairingId` string, required
    - `name` string
    - `nodeId` string: Location for the new screen.
    - `code` string: The 6-digit code the screen shows. When given, the item is claimed only if it matches; a wrong code counts toward the same lockout as `POST /v1/screens/claim`.

## Response `200`

Success.

- object
  - `data` object, required
    - `claimed` object[], required
      - `pairingId` string, required
      - `screenId` string, required
      - `name` string, required
    - `skippedNetworkCap` integer: Items with no `code` that were skipped because this network reached its hourly limit of claims without a code.

## Other responses

- `401`: Missing, expired or revoked bearer token.
- `403`: The token lacks the permission this operation needs (see `x-brix-permission`).
- `409`: The account is suspended or cancelled.
- `422`: `items` is empty.
- `429`: Too many wrong codes; claiming by code is locked for a while.
- `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)