Get one task by its per-project index
Changed onReturns a single task identified by its per-project index. Useful when resolving human-readable references like "PROJ-42" to a canonical task object. The project path parameter accepts either a numeric project id or the project's identifier (e.g. "PROJ"); values consisting solely of digits are always interpreted as ids. Note that task indexes are reassigned when a task is moved between projects, so long-lived references should use the returned task id instead.
Request
- Base URL/api/v1 (relative, and the document was published on a file host, not at the API’s origin)
- URL/api/v1/projects/{project}/tasks/by-index/{index}
- AuthAPI key in header Authorization
Path parameters
The project id or the project's identifier
The task's per-project index
Query parameters
If set to subtasks, Vikunja will fetch only tasks which do not have subtasks and then in a second step, will fetch all of these subtasks. This may result in more tasks than the pagination limit being returned, but all subtasks will be present in the response. You can only set this to subtasks.
Response
The task
Changes
- info
endpoint added
- info
- breaking
api path removed without deprecation
- breaking