Update task order within a pool

Updates the horizontal priority order of tasks within a pool for a specific accountable user. Tasks are ordered from left to right, with tasks on the left having higher priority.

Important: The pool contains tasks filtered by the Accountable field (not the Assigned field). Only tasks where the accountableId user is set as the Accountable person are included in the pool.

This endpoint updates the PoolOrder table, which stores the custom sort order for tasks within each accountable user’s pool. The order is used when displaying tasks in the pool view, allowing users to prioritize which tasks should be handled first.

The newOrder array should contain all task IDs that need to be reordered, in the desired priority sequence (first item = highest priority, leftmost position).

Permission requirements:

Pool.canEditAll: Can edit any user’s pool order
Pool.canEditOwnTeams: Can edit pools of users in the same team (requires team membership verification)
Pool.canEditOwn: Can only edit your own pool order (accountableId must match authenticated user.id)

The accountableId must reference a valid user in the same workspace who is not deleted.

POST/tasks/pool/order

Authorization

AuthorizationOAuth2 access token · headerrequired

Scopes:api:write

AuthorizationBearer token (JWT) · headerrequired

Request body

requiredapplication/json

accountableIdstringrequired

UUID of the accountable user whose pool task order should be updated. The user must exist in the same workspace and not be deleted. Access is controlled by Pool edit permissions (canEditAll, canEditOwnTeams, or canEditOwn).

newOrderstring[]required

Array of task UUIDs in the desired priority order. Tasks are displayed horizontally from left to right, with the first item in the array appearing on the left (highest priority). The array should contain all task IDs that need to be reordered. Each task ID must be a valid UUID of a task where the specified accountableId user is set as the Accountable person (filtered by Accountable field, not Assigned field).

Responses

200

Successfully updated task order

successboolean

400

Invalid accountableId UUID format or invalid newOrder array

401

Unauthorized - Invalid or missing authentication token

403

User lacks required Pool edit permissions

404

User (accountableId) not found, deleted, or not in same workspace

Try it

Server

Base URLCustom base URLOverrides the selected server when set.

Authorization

OAuth2 access tokenRemember on this deviceInclude my values in samples

Bodyapplication/json

Request body

Request

curl -X POST "https://leadtime.app/api/public/tasks/pool/order" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "accountableId": "aff55c87-49c6-4d5d-9b0b-bf7478e2d504",
  "newOrder": [
    "550e8400-e29b-41d4-a716-446655440000",
    "6ba7b810-9dad-11d1-80b4-00c04fd430c8",
    "6ba7b811-9dad-11d1-80b4-00c04fd430c8"
  ]
}'

const response = await fetch("https://leadtime.app/api/public/tasks/pool/order", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_ACCESS_TOKEN",
    "Content-Type": "application/json"
  },
  body: "{\n  \"accountableId\": \"aff55c87-49c6-4d5d-9b0b-bf7478e2d504\",\n  \"newOrder\": [\n    \"550e8400-e29b-41d4-a716-446655440000\",\n    \"6ba7b810-9dad-11d1-80b4-00c04fd430c8\",\n    \"6ba7b811-9dad-11d1-80b4-00c04fd430c8\"\n  ]\n}"
});

import requests

response = requests.post(
    "https://leadtime.app/api/public/tasks/pool/order",
    headers={
        "Authorization": "Bearer YOUR_ACCESS_TOKEN",
        "Content-Type": "application/json"
    },
    data="{\n  \"accountableId\": \"aff55c87-49c6-4d5d-9b0b-bf7478e2d504\",\n  \"newOrder\": [\n    \"550e8400-e29b-41d4-a716-446655440000\",\n    \"6ba7b810-9dad-11d1-80b4-00c04fd430c8\",\n    \"6ba7b811-9dad-11d1-80b4-00c04fd430c8\"\n  ]\n}",
)

Response

{
  "success": true
}