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

# Devices API

Register and remove push notification tokens.

| Method   | Path       | Scope           |
| -------- | ---------- | --------------- |
| `POST`   | `/devices` | `devices:write` |
| `DELETE` | `/devices` | `devices:write` |

Narrow by design: this registers push tokens so a mobile client can be woken for an incoming call or message. It is only relevant if you are building your own client.

## Register a device

```bash
curl -X POST https://app.limecall.com/api/v1/devices \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"token":"<push-token>","platform":"ios"}'
```

| Field      | Notes                                    |
| ---------- | ---------------------------------------- |
| `token`    | The push token from APNs or FCM.         |
| `platform` | Which push service the token belongs to. |

## Remove a device

```bash
curl -X DELETE https://app.limecall.com/api/v1/devices \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{"token":"<push-token>"}'
```

Identified by `token` in the body, not by an id in the path.

## Keep the registry clean

Push tokens rotate — on reinstall, on restore to a new phone, and at the OS's discretion. Re-register on every app launch rather than once at install, and delete the token on sign-out.

Stale tokens are not harmless: they accumulate, and delivery to dead tokens is what gets a sender throttled by the push services.

## If you are not building a client

You do not need this. To take calls on a phone or desk handset, use the supported options in [Devices](/virtual-numbers/devices.md) — browser, forwarding, or a SIP handset.
