> 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/qna/admin-panel/bulk-upload-devices.md).

# Bulk upload devices

Activate multiple devices in bulk by uploading CSV-XLSX to Support or using the tracker/register API endpoint with device specifications

## Question

How do I activate multiple devices at once?

## Answer

Option 1: contact Support with a CSV/XLSX containing:

* model
* label
* device\_id (IMEI)
* phone (cannot be null)
* apn\_name
* apn\_user
* apn\_password

Option 2: use the API `tracker/register` in a loop. By default, you can use `plugin_id: 44`.

Example request:

```bash
curl -X POST 'https://api.us.navixy.com/v2/tracker/register' \
  -H 'Content-Type: application/json' \
  -d '{
    "hash": "[HASH]",
    "label": "Courier",
    "group_id": 0,
    "plugin_id": 44,
    "model": "qlgv55lite",
    "phone": "79123122312",
    "device_id": "123451234512346",
    "apn_name": "fast.tmobile.com",
    "apn_user": "tmobile",
    "apn_password": "tmobile"
  }'
```

## Links

* [API: tracker/register](/docs/navixy-api/user-api/resources/tracking/tracker.md#post-tracker-register)
* [Bulk activation](/docs/admin/devices/bulk-activation.md)
* [Automatic device activation](/docs/user/guide/quick-start/activate-gps-device.md#activate-gps-device-automatically)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://navixy.com/docs/qna/admin-panel/bulk-upload-devices.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.