# Mobile app register

{% hint style="warning" %}
**Deprecated!**\
This API action deprecated and should not be used.
{% endhint %}

API call to register a mobile application. Use [tracker/register](/docs/navixy-api/user-api/backend-api/resources/tracking/tracker.md#register) with `plugin_id` 35.

## API actions

API base path: `/tracker/mobile`.

### register

Registers new mobile client application.

**required sub-user rights:** `tracker_register`.

#### Parameters

Part of parameters are registration plugin-specific. See "Registration plugins" section.

Common parameters are:

| name                     | description                                                                                                                                                                                    | type    | format          |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | --------------- |
| label                    | User-defined label for this tracker. Must consist of printable characters and have length between 1 and 60.                                                                                    | string  | "Courier"       |
| group\_id                | Tracker group id, 0 if tracker does not belong to any group. The specified group must exist. See [group/list](/docs/navixy-api/user-api/backend-api/resources/tracking/tracker/group.md#list). | int     | 0               |
| device\_id               | **Must** be specified if device model uses fixed device id. See [tracker/list\_models](/docs/navixy-api/user-api/backend-api/resources/tracking/tracker.md#list_models).                       | string  | "4568005588562" |
| send\_register\_commands | Indicates send or not to send activation commands to device (via SMS or GPRS channel). If parameter is not specified or equals `null` will be used the platform settings. Default: `null`.     | boolean | true/false      |

#### Response

```json
{
  "success": true,
  "value": {<tracker>}
}
```

For `tracker` object structure, see [tracker/](https://github.com/SquareGPS/navixy-api/blob/master/docs/user-api/introduction/resources/tracking/tracker/broken-reference/README.md).

#### Errors

* 13 – Operation not permitted – if user has insufficient rights.
* 204 – Entity not found - if specified group does not exist.
* 221 – Device limit exceeded - if device limit set for the user's dealer has been exceeded.
* 224 – Device ID already in use - if specified device ID already registered in the system.
* 225 – Not allowed for this legal type - if tariff of the new device is not compatible with user's legal type.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://navixy.com/docs/navixy-api/user-api/backend-api/resources/tracking/tracker/mobile.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.