GoliathDevelopersGet an API key
Reference/Employeesgenerated from the gateway manifest

detachEmployeePhoneLine

Release a phone line an AI employee still holds from before lines were shared.

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

Release a phone line an AI employee still holds from before lines were shared (an id from getEmployee legacyPhoneLines). It cannot be attached back, since lines are no longer assigned to employees: it stops answering calls to that number and no longer takes on new people who text it. Refused when the line is not on this employee. On an employee that is switched on it takes effect on its next run: needs their yes; a card’s counts.

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": "detachEmployeePhoneLine",
    "variables": {
      "employeeId": "<employeeId>",
      "phoneLineId": "<phoneLineId>"
    }
  }'
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.detachEmployeePhoneLine(
  {
    employeeId: '<employeeId>',
    phoneLineId: '<phoneLineId>'
  },
  { 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: 'detachEmployeePhoneLine',
    variables: {
      employeeId: '<employeeId>',
      phoneLineId: '<phoneLineId>'
    }
  }),
})
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.

employeeIdID!required
phoneLineIdID!required

Response

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

response shape
{
  "data": {
    "aiEmployeesMutation": {
      "detachContactAgentPhoneLine": {
        "id": "<ID>",
        "legacyPhoneLines": [
          {
            "id": "<ID>",
            "e164Number": "…"
          }
        ],
        "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