> For the complete documentation index, see [llms.txt](https://docs.codemash.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codemash.io/cloud/push/devices/details.md).

# Device details

One registered device.

> Everything stored about one registered device — its platform, its token, and the user it belongs to.

*Last updated 2026-09-11 · Applies to any project with the Push module enabled*

## Why it exists

When a campaign reaches nine people out of ten, the tenth is usually a device problem: the wrong platform, a token that has been rotated, or a device attached to the wrong user. A per-device view is where that is checked.

## When you'd use it

* One user never receives anything and you want to see whether a device is registered at all.
* A tester swapped phones and you want to confirm the new token replaced the old one.

## Where to find it

Push → Devices → click a device · `/projects/<project>/push/devices/<deviceId>`

{% hint style="danger" %}
This screen is **not available yet** — the address is reserved in the application's routes, but no component is mounted for it, and the [device list](/cloud/push/devices.md) it would be opened from is empty because the V2 gateway has no device-listing endpoint. Tracked in testing-plan area **15-push**.
{% endhint %}

## What to do instead

Requires a role that carries `…:notifications:push:device:read-all` (or `…:read-all:own`).

1. Keep the device id (`pnd_…`) returned by **Register device** in your own application, next to the user.
2. When a user reports a problem, re-register the device — the call is safe to repeat and refreshes a rotated token.
3. To confirm a send actually reached a device, read the campaign's batch notifications instead: they record the recipient and the delivery family. See [Message log](/cloud/push/campaigns/log.md).

## Good to know

* A device id is stable, a token is not. Build your own link from user → device id, and let Norbix hold the token.
* A device registered against the wrong user is not an error anywhere — it simply means the notification goes to the wrong phone. Register with the user id you authenticated, never one taken from the client.

## Do it in code

Registration is the only device operation available today; see [Devices](/cloud/push/devices.md) for the snippets in all four languages.

Reference: [Register Device](/sdks-and-cli/notifications/push/register-device.md) CLI: no device commands today.

## API reference

Endpoints: [Register Device](/api-reference/notifications/push/register-device.md).

## Related

[Devices](/cloud/push/devices.md) · [Campaigns](/cloud/push/campaigns.md) · [Message log](/cloud/push/campaigns/log.md)