Task history

The record of how a task's fields and state changed over its life.

The Navixy platform records every change to a task's fields and its state, and this operation reads that record. It answers who changed what and when, which matters when a task's outcome is disputed after the fact.

History entry

API actions

API base path: /task/history.

Operations that list no errors of their own return only the general error codes.

---

List task history

post

/task/history/list

Return the recorded history of one task: its creation, updates, assignments and status changes.

Also accepts GET with the same parameters as query-string values.

Authorizations

AuthorizationstringRequired

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.

Body

task_idinteger · min: 1Required

ID of the task.

Responses

200

The task history

application/json

successbooleanRead-onlyOptional

true if request finished successfully.

Example: true

400

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.

application/json

default

Error response object

application/json

post/task/history/list

POST /v2/task/history/list HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 13

{
  "task_id": 1
}

{
  "success": true,
  "list": [
    {
      "id": 1,
      "user_id": 1,
      "task_id": 1,
      "event_date": "text",
      "operation": "create",
      "payload": {
        "ANY_ADDITIONAL_PROPERTY": "anything"
      }
    }
  ]
}