removeCallListContacts

Take contacts off a call list before they are called: their slots close as skipped by hand (skipReason USER), so the list keeps its record. A contact being dialed right now, already called, or up next for a rep working the list stays as it is and counts in notRemovedCount. A removed contact keeps its slot (and its place toward the 10,000 cap) and cannot be added back to the same list. Needs you to have built the list or be an admin. Refused on an ENDED list.

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": "removeCallListContacts",
    "variables": {
      "callListId": "<callListId>",
      "contactIds": [
        "<contactIds>"
      ]
    }
  }'

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.callLists.removeCallListContacts(
  {
    callListId: '<callListId>',
    contactIds: [
      '<contactIds>'
    ]
  },
  { 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: 'removeCallListContacts',
    variables: {
      callListId: '<callListId>',
      contactIds: [
        '<contactIds>'
      ]
    }
  }),
})
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.

callListIdID!required

contactIds[ID!]!required

Response

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

response shape

{
  "data": {
    "callListsMutation": {
      "removeCallListContacts": {
        "callList": {
          "id": "<ID>",
          "name": "…",
          "status": "…",
          "visibilityScope": "…",
          "maxNumbersPerContact": 0,
          "includeRelatives": true,
          "overrideDnc": true,
          "overrideLitigator": true,
          "cursorPosition": 0,
          "startedAt": "2026-01-01T00:00:00.000Z",
          "endedAt": "2026-01-01T00:00:00.000Z",
          "dialPath": "…",
          "createdByUser": {
            "id": "<ID>",
            "firstName": "…",
            "lastName": "…"
          },
          "lockedByUser": {
            "id": "<ID>",
            "firstName": "…",
            "lastName": "…"
          },
          "reachedTag": {
            "id": "<ID>",
            "name": "…"
          },
          "counts": {
            "total": 0,
            "pending": 0,
            "completed": 0,
            "skipped": 0,
            "dials": 0,
            "byDisposition": [
              {
                "disposition": "…",
                "count": 0
              }
            ]
          }
        },
        "removedCount": 0,
        "notRemovedCount": 0
      }
    }
  }
}

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 →

Variables

Response

Errors

Idempotency

Related