Read the work queue

GET

/api/v1/work-queue

const url = 'https://app.avera.io/api/v1/work-queue';
const options = {method: 'GET'};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://app.avera.io/api/v1/work-queue

What the queried users owe, derived from current state rather than task rows: endorsement slots they can fill and transitions they can fire. Without userIds it is the caller’s own queue across every tenant they actively participate in; with userIds it is the manager view, scoped to the active tenant, gated per project by the queue.read capability and audited per request. Entries deep-link only: disposition happens in the item’s transition dialog.

Parameters

Query Parameters

userIds

Array<string>

Responses

200

*/*

object

users

required

Array<object>

object

userId

required

string format: uuid

inbound

required

Array<object>

object

kind

required

string

tenantId

required

string format: uuid

tenantSlug

required

string

tenantName

required

string

projectId

required

string format: uuid

projectKey

required

string

branchKey

required

string

itemId

required

string format: uuid

itemNumber

required

string

itemTypeId

required

string

itemTypeIcon

string | null

itemTypeColor

string | null

itemStatus

required

string

transitionId

required

string

transitionName

required

string

principalSlot

string | null

needsSignature

required

boolean

stale

required

boolean

since

required

string format: date-time

proposals

required

Array<object>

object

tenantId

required

string format: uuid

tenantSlug

required

string

tenantName

required

string

projectId

required

string format: uuid

projectKey

required

string

branchKey

required

string

pendingCount

required

integer format: int32

unreadComments

integer | null format: int32