# listFilterFieldNames

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.

- Call: `POST https://server.goliathdata.com/api/v1/call` with `{ "operationId": "listFilterFieldNames", "variables": {...} }`
- Scope: `READ`
- Type: query
- Idempotency: a read; rejects `Idempotency-Key`
- Rate-limited: no

## Variables

- `type`: `FilterType!` (required, one of `PROPERTY`, `CONTACT`, `PIPELINE_ITEM`, `DEAL`, `OWNER`, `POST`, `ENTITY`, `PERSON`, `USER`, `ORGANIZATION`)

## Response (data, an example)

```json
{
  "filterQuery": {
    "listFilterFields": [
      {
        "fieldId": "<ID>",
        "label": "…",
        "category": "…",
        "component": "…"
      }
    ]
  }
}
```

## Example

```bash
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"
    }
  }'
```