---
title: "Register the calling device"
method: POST
path: "/user/register-mobile-device"
tags: ["user"]
---

# Register the calling device

`POST /user/register-mobile-device`

## Request

- Base URL: `https://vetnio.com/api/v2`
- URL: `https://vetnio.com/api/v2/user/register-mobile-device`
- Auth: HTTP bearer

Labels the device that owns the API key used to make this request, so it appears under the user's connected devices in the web app and can be revoked individually. The mobile app calls it right after pairing with the key obtained from the QR-code flow. Must be called with an API key in the `Authorization` header (a session gets 400). The key is marked as a mobile-device key, which removes it from the user's programmatic API-key list, so do not call this with a key used for server integrations. Safe to repeat.

## Request body

- object: Self-reported details of the device that owns the calling API key.
  - `deviceName` string: Name the device reports for itself, 1-60 characters after trimming. Applied only while the key still has the default name `New device`; a name the user typed in the web app when pairing always wins. Omit to keep the current name.
  - `platform` string: Free-text platform label shown next to the device, up to 40 characters, for example `ios` or `android`. Omitting it or sending an empty string clears the stored platform.

## Response `200`

Device registered.

- object: Acknowledgement that the device details were saved.
  - `success` boolean, required: Always `true` when the device details were saved.

## Other responses

- `400`: Invalid input data
- `401`: Authorization not provided
- `403`: Insufficient access
- `500`: Internal server error

---

[API](https://skmtc.dev/vetnio/apis/vetnio-api.md) - [All operations](https://skmtc.dev/vetnio/apis/vetnio-api/llms.txt) - [OpenAPI document](https://skmtc.dev/vetnio/apis/vetnio-api/revisions/d004afd5617d?raw)