> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/user-api/resources/tracking/tracker/mobile.md). # Mobile app register Deprecated. Register a mobile application as a tracker. {% hint style="warning" %} **Deprecated.** This action should not be used. Register a mobile application with [`tracker/register`](/docs/navixy-api/user-api/resources/tracking/tracker.md#post-tracker-register) and `plugin_id` 35 instead. {% endhint %} This operation registered a phone running the mobile application as a tracker in its own right. It still answers, and is documented here because it is still reachable, but `tracker/register` covers the same ground and is maintained. As with `tracker/register`, the chosen [registration plugin](/docs/navixy-api/user-api/resources/commons/plugin.md) adds its own parameters on top of the ones the operation lists. The group must already exist. List groups with [`group/list`](/docs/navixy-api/user-api/resources/tracking/tracker/group.md#post-tracker-group-list). Models with a fixed device ID are listed by [`tracker/list_models`](/docs/navixy-api/user-api/resources/tracking/tracker.md#post-tracker-list_models). The call returns a [tracker object](/docs/navixy-api/user-api/resources/tracking/tracker.md#tracker-object-structure). ## API actions API base path: `/tracker/mobile`. *** *Required sub-user rights:* `tracker_register`. ## Register a mobile application (deprecated) > \*\*Deprecated. Do not use.\*\* Register a new mobile client application.\ > \ > Use \`tracker/register\` with \`plugin\_id\` 35 instead. As with that call, the chosen registration plugin adds its own parameters on top of the ones below.\ > \ > Requires the \`tracker\_register\` right. ```json {"openapi":"3.1.0","info":{"title":"Navixy Platform API","version":"1.0.0"},"tags":[{"name":"Trackers","description":"Trackers, the devices the platform tracks, together with the geo links that share their live location with people outside the account. Resources under the /tracker/ path."}],"servers":[{"url":"https://api.eu.navixy.com/v2","description":"Navixy production server on European platform"},{"url":"https://api.us.navixy.com/v2","description":"Navixy production server on American platform"},{"url":"https://api.me.navixy.com/v2","description":"Navixy production server on Middle East platform"}],"security":[{"api_key":[]}],"components":{"securitySchemes":{"api_key":{"type":"apiKey","description":"Either a user session hash or an API key, with the \"NVX \" prefix, for example \"NVX 22eac1c27af4be7b9d04da2ce1af111b\". Obtain a session hash from the userAuth operation, or create an API key from the API keys operations. A small number of operations accept a session hash only and reject an API key with error code 4; each says so in its description.","name":"Authorization","in":"header"}},"schemas":{"Tracker":{"type":"object","description":"A tracking device registered in the platform. One of the central objects of this API.","properties":{"id":{"type":"integer","description":"Tracker ID, also known as the object ID."},"label":{"type":"string","description":"Tracker label."},"clone":{"type":"boolean","description":"`true` when this tracker is a clone of another."},"group_id":{"type":"integer","description":"Tracker group ID, `0` when the tracker is in no group."},"avatar_file_name":{"type":"string","description":"Avatar file name. Present only when the tracker has one."},"source":{"$ref":"#/components/schemas/TrackerSource"},"tag_bindings":{"type":"array","description":"Tags attached to the tracker. Returned by `tracker/list`, and by the registration and replacement calls.","items":{"$ref":"#/components/schemas/TagBinding"}}}},"TrackerSource":{"type":"object","description":"The physical device behind a tracker.","properties":{"id":{"type":"integer","description":"Source ID."},"device_id":{"type":"string","description":"Device ID, also called the source IMEI. Its accepted shape depends on the model's `id_type`."},"model":{"type":"string","description":"Model code, as returned by `tracker/list_models`."},"blocked":{"type":"boolean","description":"`true` when the tracker is blocked because its tariff ended."},"tariff_id":{"type":"integer","description":"ID of the tracker's tariff."},"status_listing_id":{"type":["integer","null"],"description":"ID of the working status list assigned to this tracker, or null."},"creation_date":{"type":"string","description":"Date the tracker was registered, `YYYY-MM-DD`."},"tariff_end_date":{"type":["string","null"],"description":"Date of the next tariff prolongation, `YYYY-MM-DD`, or null."},"phone":{"type":["string","null"],"description":"Phone number of the device. Null or empty when the device has no GSM module, or uses a bundled SIM whose number is hidden from the user."}}},"TagBinding":{"type":"object","description":"A tag attached to a tracker.","properties":{"tag_id":{"type":"integer","description":"ID of the tag. Unique within a tracker."},"ordinal":{"type":"integer","description":"Position or kind of the tag. Unique within a tracker, maximum 5.","minimum":1,"maximum":5}},"required":["tag_id","ordinal"]}},"responses":{"ResponseError":{"description":"Error response object","content":{"application/json":{"schema":{"type":"object","properties":{"success":{"type":"boolean","description":"Always false."},"status":{"type":"object","description":"Error status. Present only when an error occurred.","properties":{"code":{"type":"integer","description":"An error code in this API, not an HTTP code."},"description":{"type":"string","description":"An error description."}}},"errors":{"type":"array","description":"Per-parameter detail, returned with validation failures such as error code 7. A parameter name here may be an internal field name rather than the documented parameter name.","items":{"type":"object","properties":{"parameter":{"type":"string","description":"Name of the parameter that failed validation."},"error":{"type":"string","description":"What was wrong with it."}}}}}}}}}}},"paths":{"/tracker/mobile/register":{"post":{"tags":["Trackers"],"summary":"Register a mobile application (deprecated)","description":"**Deprecated. Do not use.** Register a new mobile client application.\n\nUse `tracker/register` with `plugin_id` 35 instead. As with that call, the chosen registration plugin adds its own parameters on top of the ones below.\n\nRequires the `tracker_register` right.","operationId":"trackerMobileRegister","requestBody":{"required":true,"content":{"application/json":{"schema":{"type":"object","properties":{"label":{"type":"string","description":"User-defined label. Printable characters, 1 to 60.","minLength":1,"maxLength":60},"group_id":{"type":"integer","description":"Tracker group ID, or `0` for no group. The group must exist."},"device_id":{"type":"string","description":"Required when the model uses a fixed device ID."},"send_register_commands":{"type":["boolean","null"],"description":"Optional. Default null, meaning follow the platform setting."}},"required":["label","group_id"],"additionalProperties":true}}}},"responses":{"200":{"description":"The registered tracker","content":{"application/json":{"schema":{"type":"object","properties":{"success":{"type":"boolean","description":"`true` if request finished successfully.","readOnly":true},"value":{"$ref":"#/components/schemas/Tracker"}}}}}},"400":{"description":"Bad request. The response body carries the API-level error code in `status.code`. Validation failures also include an `errors` array naming each offending parameter.","$ref":"#/components/responses/ResponseError"},"403":{"description":"Error 13: the user lacks the right. Error 204: the group does not exist. Error 221: the dealer's device limit is exceeded. Error 224: the device ID is already registered. Error 225: the tariff is not compatible with the account's legal type.","$ref":"#/components/responses/ResponseError"},"default":{"$ref":"#/components/responses/ResponseError"}}}}}} ``` #### Errors These errors come in addition to the [general error codes](/docs/navixy-api/general/errors.md#error-codes): * 13 - The user lacks the right. * 204 - The group does not exist. * 221 - The dealer's device limit is exceeded. * 224 - The device ID is already registered. * 225 - The tariff is not compatible with the account's legal type. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://navixy.com/docs/navixy-api/user-api/resources/tracking/tracker/mobile.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.