Skip to content

Get Desk Batch

GET
/desk/batch

This rep’s batch for their local day.

data is NULL when no batch has been started today. That is different from a batch with nothing left in it, and the difference decides whether a UI shows “start your day” or “you are done” - so it is preserved rather than flattened into an empty batch.

The app’s include=overview composite is deliberately not exposed: it returns a different response shape from the same path, which is a shell optimisation rather than a contract a rebuilder should depend on.

Authorizations

Parameters

Query Parameters

tz_offset

The rep’s UTC offset in MINUTES (local = UTC + tz_offset). A batch is scoped to the rep’s local day; a wrong offset silently returns the wrong day rather than erroring.

integer
>= -840 <= 840

The rep’s UTC offset in MINUTES (local = UTC + tz_offset). A batch is scoped to the rep’s local day; a wrong offset silently returns the wrong day rather than erroring.

Header Parameters

X-Target-Org-Id
Any of:
string

Responses

200

Successful Response

object
data
required
Any of:

Today’s frozen batch.

A batch is FINITE by design: the rep freezes a ranked slice of the queue so the day has an end. None from the app means no batch has been started today, which is different from a batch with no items left - the response keeps that distinction rather than flattening both to an empty batch.

object
completed
Any of:
integer
completed_at
Any of:
string format: date-time
id
Any of:
string
item_ids
Array<string>
remaining
Any of:
integer
started_at
Any of:
string format: date-time
status
Any of:
string
total
Any of:
integer
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string