---
title: "Socket.IO: Single device"
description: "Receive the events of ONE device only. The filter is not in the connection: the service emits a frame whose NAME is the device token, so you listen for that name."
lang: en
canonical: https://doc.apibrasil.io/socket-io/unique-device
markdown: https://doc.apibrasil.io/socket-io/unique-device.md
source: apibrasil-documentation
---

# Socket.IO: Single device

> Receive the events of ONE device only. The filter is not in the connection: the service emits a frame whose NAME is the device token, so you listen for that name.

- **Address:** `https://socket.apibrasil.com.br`

**Parameters of this connection**

- `bearer` (required): The same Bearer Token you use on the API. It is the only parameter checked at the door: without it the connection is refused with “Token de autenticação não fornecido”, and with a token that does not validate, with “Token de autenticação inválido”.
- `channelName` (required): The room you join. It is how the service decides what to deliver to you, and it is your Profile ID — the same value the gateway uses when publishing. Without it the connection COMES UP but you join no room at all: no event arrives, and no error is shown.

**What to listen to**

- `{deviceToken}` — the event name is the device token. THE EVENT NAME IS THE DEVICE TOKEN. It is not a mistake:
  the service emits a frame under that name, and that is how you
  listen to a single handset.

The details of each parameter, of the frames and of the pitfalls are on the general Socket.IO page. [Socket.IO](https://doc.apibrasil.io/socket-io.md)

## See also

- Documentation index: https://doc.apibrasil.io/llms.txt
- HTML version of this page: https://doc.apibrasil.io/socket-io/unique-device