listPipelineItemActivity
One pipeline item's activity feed, most-recent-first.
One pipeline item's activity feed, most-recent-first: the audit trail behind "who changed the price on this pipeline item, and when did it get reassigned?". Each event carries eventType, createdAt, actor (the person, null for system/automation), and a SuperJSON payload whose json object holds the per-eventType detail. Pass eventTypes to narrow to the types you care about: a narrowed read pages at the DATABASE, so a sparse type's full history stays reachable however busy the rest of the feed is; omit it for the mixed feed, which caps at the 200 most recent events. Page with offset. THE FULL eventType VOCABULARY, with the payload keys under payload.json for each (there is no schema expansion for a SuperJSON scalar, so this text is the only description of the shape). The title and names are not in the payload: read the contract for them). Those twenty are the whole vocabulary: an eventType outside this list does not exist. What the feed does NOT record is edits to a pipeline item's title or custom-field values (no event type covers them, so their history is not reconstructable here) nor a description edit made through this API, an AI employee or an agent tool (DESCRIPTION_CHANGED covers only a person's own in-app edits), so no DESCRIPTION_CHANGED event does not mean the description was never changed.
curl https://server.goliathdata.com/api/v1/call \
-H "Authorization: Bearer $GOLIATH_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"operationId": "listPipelineItemActivity",
"variables": {
"pipelineItemId": "<pipelineItemId>"
}
}'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.pipelineItems.listPipelineItemActivity({
pipelineItemId: '<pipelineItemId>'
})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: 'listPipelineItemActivity',
variables: {
pipelineItemId: '<pipelineItemId>'
}
}),
})
const { data, errors } = await res.json()limit is clamped to 50.
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 50.
Response
What comes back under data: a list shows as one entry, and a value as its type.
{
"data": {
"pipelineItemQuery": {
"getPipelineItem": {
"id": "<ID>",
"events": [
{
"id": "<ID>",
"eventType": "STAGE_CHANGED",
"createdAt": "2026-01-01T00:00:00.000Z",
"actor": {
"userId": "<ID>",
"name": "…"
},
"payload": "…",
"taskNow": "…"
}
]
}
}
}
}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.