GoliathDevelopersGet an API key
Reference/Propertiesgenerated from the gateway manifest

listFilterFieldNames

The COMPLETE vocabulary of filterable fields for a domain.

POST/api/v1/callREADreadruns as the key's owner
View as Markdown

The COMPLETE vocabulary of filterable fields for a domain (CONTACT, PROPERTY or DEAL): every fieldId saveFilter accepts, with label, category and UI component. It always arrives whole, unlike the fuller listFilterFields, which drops WHOLE FIELDS when unnarrowed, so it is the only trustworthy answer to "is X filterable here?". Find the fieldId here, then call listFilterFields with those fieldIds for descriptions and value shapes. A field absent from THIS list is genuinely not filterable; never tell a user a filter is impossible from a truncated listFilterFields response or a rejected fieldId guess. Static schema introspection: reads no org data.

curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "operationId": "listFilterFieldNames",
    "variables": {
      "type": "PROPERTY"
    }
  }'
import { GoliathClient } from '@goliath-data/sdk'

const goliath = new GoliathClient({
  apiKey: process.env.GOLIATH_API_KEY!,
  baseUrl: 'https://server.goliathdata.com',
})

// Enum values as strings: the SDK's enum types aren't exported yet, so assert to the method's variables type.
const variables = {
  type: 'PROPERTY'
} as Parameters<typeof goliath.properties.listFilterFieldNames>[0]

const result = await goliath.properties.listFilterFieldNames(variables)
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',
  },
  body: JSON.stringify({
    operationId: 'listFilterFieldNames',
    variables: {
      type: 'PROPERTY'
    }
  }),
})
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.

typeFilterType!required
PROPERTYCONTACTPIPELINE_ITEMDEALOWNERPOSTENTITYPERSONUSERORGANIZATION

Response

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

response shape
{
  "data": {
    "filterQuery": {
      "listFilterFields": [
        {
          "fieldId": "<ID>",
          "label": "…",
          "category": "…",
          "component": "…"
        }
      ]
    }
  }
}

Errors

Behaviour

A read. It rejects an Idempotency-Key header with 400 bad_request.