GoliathDevelopersGet an API key
Reference/Contactsgenerated from the gateway manifest

renameContactList

Rename a contact LIST in place.

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

Rename a contact LIST in place (listId from searchContactTags lists): "rename Hot Leads to Priority Sellers". THIS IS THE CORRECT WAY TO FIX A LIST NAME: deleteContactLists plus createContactList is irreversible and drops every membership, while a rename keeps the id, so members and every saved filter and workflow pointing at the list are untouched. Applied synchronously; returns the org list catalog with the new name. LIST ids only: a free-form tag or custom-field id is refused at the gateway (renameContactTag / updateContactCustomField). The name must be non-empty, at most 100 characters, and unique among the organization's lists, or it is rejected. Only the label changes: membership is not moved, merged or re-evaluated.

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": "renameContactList",
    "variables": {
      "listId": "<listId>",
      "newName": "<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.contacts.renameContactList(
  {
    listId: '<listId>',
    newName: '<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: 'renameContactList',
    variables: {
      listId: '<listId>',
      newName: '<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.

listIdID!required
newNameString!required

Response

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

response shape
{
  "data": {
    "contactMutation": {
      "updateContactList": {
        "contactLists": [
          {
            "id": "<ID>",
            "name": "…"
          }
        ]
      }
    }
  }
}

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 →

READgetContactREADgetContactsPropertiesREADfindContactsByNoteREADsearchInteractionsREADcountContactsREADfindContacts