Source Types
Fields are organized by source type:| Source Type | Description |
|---|---|
properties | Property-related fields (address, value, lot size, etc.) |
people | Contact/owner-related fields (name, phone, email, etc.) |
Field Types
Each field has a data type that determines how its values are stored and queried:| Type | Description | Examples |
|---|---|---|
NUMBER | Numeric values | Estimated value, square footage, bedrooms |
STRING | Text values | City name, owner name, address |
DATE | Date values | Sale date, list date, year built |
MULTI_SELECT | Predefined option sets | Property type, zoning, MLS status |
BOOLEAN | True/false values | Is absentee owner, has pool, is vacant |
Field Capabilities
Each field has a capability flag that indicates how it can be used:| Capability | Description |
|---|---|
is_filterable | Can be used as a search filter |
Field Groups
Fields are organized into groups. Use thegroup_id to browse fields by category:
Discovering Fields
Use the List Fields endpoint to discover all available fields:Selecting Fields in Queries
When making a search request, use thefields parameter to control which data points appear in the response:
- Pass an array of
field_idstrings from the discovery endpoint above. - Omit
fieldsor pass an empty array to receive the default set of fields. - Some base fields (address, internal ID) are always included regardless of your selection. See Response Format.
- Requesting fewer fields results in smaller payloads and faster responses.
source_type can be requested. Use source_type=properties with Search Properties and source_type=people with Search People.
For the full search workflow, see Searching.
Fields vs Filters
- Fields describe what data is available (columns in your results)
- Filters describe how you can query that data (search criteria)
is_filterable: true have a corresponding filter. Use the List Filters endpoint to see filter-specific metadata like allowed operators and options.