GoliathDevelopersGet an API key
Reference/Employeesgenerated from the gateway manifest

createEmployee

Hire an AI employee.

POST/api/v1/callWRITEidempotent · 24 hruns as the key's owner
View as Markdown

Hire an AI employee. It is ALWAYS created switched off (INACTIVE), whatever the config says: it answers nobody until it is switched on. Omit config for the generalist an operator gets with no template (texts, emails and calls once a phone line or mailbox is attached, notes, tasks, notifying a teammate, booking its own follow-up), then shape it with updateEmployeeConfig; or pass a COMPLETE config document in the shape getEmployee returns as configDocument. The same checks the employee builder runs apply, and a refusal names each field and what to change. Returns the new employee and its configDocument.

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": "createEmployee",
    "variables": {
      "name": "<String>"
    }
  }'
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.createEmployee(
  {
    name: '<String>'
  },
  { 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: 'createEmployee',
    variables: {
      name: '<String>'
    }
  }),
})
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.

nameString!required
titleString
avatarString
originString
configJSON

Response

What comes back under data: a list shows as one entry, and a value as its type.

response shape
{
  "data": {
    "aiEmployeesMutation": {
      "createAiEmployee": {
        "id": "<ID>",
        "name": "…",
        "title": "…",
        "status": "ACTIVE",
        "configDocument": "…",
        "updatedAt": "2026-01-01T00:00:00.000Z"
      }
    }
  }
}

Errors

400unknown_variable

A variable the operation does not declare. A typo is refused rather than silently dropped.

401unauthorized

No bearer header, or the key is invalid or revoked.

403insufficient_scope

The key lacks the scope the operation requires.

403forbidden

A referenced record does not exist, was deleted, or is outside your organization. The gateway cannot tell those apart.

409idempotency_conflict

A 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 →

READlistEmployeesREADgetEmployeeREADgetEmployeeCaseloadREADlistEmployeeChannelOptionsREADlistEmployeeSuggestionsREADlistEmployeeRevisions