publishGoalPlan
Publish a DRAFT plan.
Publish a DRAFT plan (planId from getGoalPlan): it becomes the month's active plan, the one Agent Performance tracks, and the previous active plan is archived. Confirm with the user first. Your own plan; a teammate’s is the *Teammate* op (ADMIN).
curl https://server.goliathdata.com/api/v1/call \
-H "Authorization: Bearer $GOLIATH_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{
"operationId": "publishGoalPlan",
"variables": {
"planId": "<planId>"
}
}'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.team.publishGoalPlan(
{
planId: '<planId>'
},
{ idempotencyKey: crypto.randomUUID() },
)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',
'Idempotency-Key': crypto.randomUUID(),
},
body: JSON.stringify({
operationId: 'publishGoalPlan',
variables: {
planId: '<planId>'
}
}),
})
const { data, errors } = await res.json()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.
Response
What comes back under data: a list shows as one entry, and a value as its type.
{
"data": {
"agentGoalsMutation": {
"publishAgentGoalPlan": {
"id": "<ID>",
"userId": "<ID>",
"periodStartDate": "…",
"periodEndDate": "…",
"status": "DRAFT",
"publishedAt": "2026-01-01T00:00:00.000Z",
"commissionGoals": [
{
"id": "<ID>",
"pipelineId": "<ID>",
"pipelineName": "…",
"metric": "EARNED",
"targetCents": "…"
}
],
"personalGoals": [
{
"id": "<ID>",
"title": "…",
"description": "…",
"status": "ACTIVE",
"displayOrder": 0
}
]
}
}
}
}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.
idempotency_conflictA request with this Idempotency-Key is still in flight.
Idempotency
Send an Idempotency-Key of 1 to 255 characters. A finished request retried with the same key replays its stored response, marked Idempotency-Replayed: true; one still in flight returns 409 idempotency_conflict. Keys expire after 24 hours. Write without fear →