# Task history

Navixy platform tracks changes to task fields and state for your convenience.Our platform tracks changes to task fields and state for your convenience. Contains API calls to get this information.

## History entry

```json
{
    "id": 22,
    "user_id": 3,
    "task_id": 1,
    "event_date": "2014-08-05 10:54:55",
    "operation": "assign",
    "payload": {
    "tracker_id": 2470
    }
}
```

* `id` - int. Entry ID.
* `user_id` - int. User ID.
* `task_id` - int. An ID of the task with which this entry associated.
* `event_date` - [date/time](/docs/navixy-api/user-api/backend-api.md#data-types). Date when history event happened.
* `operation` - [enum](/docs/navixy-api/user-api/backend-api.md#data-types). Operation which happened. Can be "create", "update", "assign" or "status\_change".
* `payload` - depends on operation. Typically, contains fields which were changed during operation.

## API actions

API base path: `task/history`.

### list

Returns history for the task with the specified ID.

#### Parameters

| name     | description     | type |
| -------- | --------------- | ---- |
| task\_id | ID of the task. | int  |

#### Examples

{% tabs %}
{% tab title="cURL" %}

```sh
curl -X POST 'https://api.eu.navixy.com/v2/task/checkpoint/delete' \
    -H 'Content-Type: application/json' \
    -d '{"hash": "22eac1c27af4be7b9d04da2ce1af111b", "checkpoint_id": 23144}'
```

{% endtab %}

{% tab title="HTTP GET" %}
{% code overflow="wrap" %}

```http
https://api.eu.navixy.com/v2/task/checkpoint/delete?hash=a6aa75587e5c59c32d347da438505fc3&checkpoint_id=23144
```

{% endcode %}
{% endtab %}
{% endtabs %}

#### Response

```json
{
    "success": true,
    "list": [{
         "id": 22,
         "user_id": 3,
         "task_id": 1,
         "event_date": "2014-08-05 10:54:55",
         "operation": "assign",
         "payload": {
         "tracker_id": 2470
         }
    }]
}
```

#### Errors

* [General](/docs/navixy-api/user-api/backend-api/errors.md#error-codes) types only.


---

# 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/field-service/task/history.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.