Skip to main content
The individual data points available for properties and people in DealMachine. Each field has a type, a source, and capabilities that determine how it can be used.

​
Source Types

Fields are organized by source type:

​
Field Types

Each field has a data type that determines how its values are stored and queried:

​
Field Capabilities

Each field has a capability flag that indicates how it can be used:

​
Field Groups

Fields are organized into groups. Use the group_id to browse fields by category:
See the Groups page for the complete list of all group IDs.

​
Discovering Fields

Use the List Fields endpoint to discover all available fields:
You can filter by source type, group, or search by name:

​
Selecting Fields in Queries

Use the fields parameter to control which data points appear in supported search, lookup, export, and enrichment responses:
  • Pass an array of field_id strings from the discovery endpoint above.
  • Omit fields or 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.
  • In a people-anchored property search, requesting property fields beyond address/context adds property credits. Filters do not add output credits by themselves. See Credit-efficient queries before selecting fields for mixed property and people searches.
Only fields available for your chosen source_type can be requested. Use source_type=properties with Search Properties and source_type=people with Search People. For example, has_pets is an API-available people field and people filter. Request it from a people lookup, people search, person enrichment, or a search with a people result anchor. It is not a property attribute and is not returned by GET /v1/properties/{id}. The following public Endpoints accept fields: GET /v1/addresses/autocomplete is intentionally discovery-only and does not accept fields or perform enrichment. Select a suggestion first, then send its address or normalized location to the appropriate search or enrichment Endpoint with the fields you need. 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)
Fields with is_filterable: true have a corresponding filter. Use the List Filters endpoint to see filter-specific metadata like allowed operators and options.