getEmployeeCaseload
The contacts one AI employee is on, newest attachment first, offset-paged.
The contacts one AI employee is on, newest attachment first, offset-paged (offset, limit; total is the full count). Each row says whether it is working that contact now, when it last worked it, the next run of a repeating schedule (attachment.schedule), the soonest follow-up it booked itself (nextBookedFollowUpAt, null when none), and whether the contact replied or escalated. A new touch on a contact with one booked comes before that follow-up. includeRemoved: true adds contacts a person took it off.
curl https://server.goliathdata.com/api/v1/call \
-H "Authorization: Bearer $GOLIATH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"operationId": "getEmployeeCaseload",
"variables": {
"employeeId": "<employeeId>"
}
}'import { GoliathClient } from '@goliath-data/sdk'
const goliath = new GoliathClient({
apiKey: process.env.GOLIATH_API_KEY!,
baseUrl: 'https://server.goliathdata.com',
})
const result = await goliath.employees.getEmployeeCaseload({
employeeId: '<employeeId>'
})const res = await fetch('https://server.goliathdata.com/api/v1/call', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.GOLIATH_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
operationId: 'getEmployeeCaseload',
variables: {
employeeId: '<employeeId>'
}
}),
})
const { data, errors } = await res.json()limit is clamped to 100.
Variables
The example sends only what the schema requires. Some operations also need one of several optional variables (one filter or another, say); the description above says which.
Default 0.
Default 25.
Response
What comes back under data: a list shows as one entry, and a value as its type.
{
"data": {
"aiEmployeesQuery": {
"contactAgentCaseload": {
"total": 0,
"items": [
{
"contactId": "<ID>",
"contactName": "…",
"isWorkingNow": true,
"lastWorkedAt": "2026-01-01T00:00:00.000Z",
"lastCommunicationAt": "2026-01-01T00:00:00.000Z",
"nextBookedFollowUpAt": "2026-01-01T00:00:00.000Z",
"attachment": {
"id": "<ID>",
"source": "MANUAL",
"status": "ACTIVE",
"createdAt": "2026-01-01T00:00:00.000Z",
"schedule": {
"nextFireAt": "2026-01-01T00:00:00.000Z"
},
"engagement": {
"receivedReply": true,
"positivelyEscalated": true,
"negativeIntent": true
}
}
}
]
}
}
}
}Errors
unknown_variableA variable the operation does not declare. A typo is refused rather than silently dropped.
unauthorizedNo bearer header, or the key is invalid or revoked.
insufficient_scopeThe key lacks the scope the operation requires.
forbiddenA referenced record does not exist, was deleted, or is outside your organization. The gateway cannot tell those apart.
Behaviour
A read. It rejects an Idempotency-Key header with 400 bad_request.