# Datalogger

## API actions

API base path: `/tracker/datalogger`.

### upload

Uploads track data for specified tracker. Tracker must be a datalogger.

**MUST** be a POST multipart request (multipart/form-data), with one of the parts being a CSV file upload\
(with the name "file").

#### Parameters

| name        | description                                                                                      | type |
| ----------- | ------------------------------------------------------------------------------------------------ | ---- |
| tracker\_id | ID of the tracker (aka "object\_id"). Tracker must belong to authorized user and not be blocked. | int  |
| file        | A CSV file upload containing datalogger track data.                                              | file |

#### Response

```json
{
  "success": true
}
```

#### Errors

* 201 – Not found in the database - if there is no tracker with such ID belonging to authorized user.
* 219 – Not allowed for clones of the device - if tracker is clone.
* 233 – No data file - if file part is missing.
* 214 – Requested operation or parameters are not supported by the device - if specified tracker is not datalogger.


---

# 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/datalogger.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.