SiftMap is the nationwide property layer: search any US property by location and criteria, read its full record, and add the ones you want to your DataSift account. Saved map filters can feed matching properties into your account automatically.
SiftMap requests use https://map.reisift.io and the same Authorization: Api-Key header as other DataSift requests. Full reference: the SiftMap group in the DataSift API reference. Criteria keys: SiftMap filter reference.
POST /properties/search/ takes a location, criteria, or both:
curl -X POST https://map.reisift.io/properties/search/ \
-H "Authorization: Api-Key YOUR_OPEN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"addresses": [{"type": "county", "search": "Franklin", "state": "OH"}],
"filters": {
"type_single_family": true,
"value_max": 700000,
"extra_mls_status": ["not_listed"],
"distressors_include": "is_vacant_property",
"distressors_include_min_match": 1
},
"size": 25,
"result_index": 0
}'| Field | Meaning |
|---|---|
addresses | Locations to search: {"type": "state" | "county" | "city" | "zip" | "address", "search": "...", "state": "OH"}. County and city need state. |
polygon | A map area: a closed ring of {"lat": ..., "lon": ...} points. |
filters | Property criteria. See the filter reference. |
size | Results per page. Keep it at 25-100. |
result_index | Zero-based index of the first result (offset). |
Provide at least one of addresses, polygon or filters. The response:
{
"result_index": 0,
"total_pages": 155,
"page_results": 25,
"total_results": 3853,
"polygon": [],
"data": [
{
"id": "102752166",
"address": "123 Main St, Columbus, OH 43207",
"county": "Franklin", "state": "OH", "fips": "39049",
"bedrooms": 2, "bathrooms": 2, "squareFeet": 936.0,
"estimatedValue": 85000.0, "equityPercent": 100,
"absenteeOwner": true, "mlsActive": false,
"saved": false, "saved_uuid": null,
"investor_on_market_score": 78, "realtor_score": 19
}
]
}saved and saved_uuid tell you whether the property is already in your account. Unknown filter keys are ignored, so check total_results with size: 1 when you change criteria.
GET /properties/detail/{property_id}/ returns the full nationwide record for one property: building and lot, tax and assessment, sale and mortgage history, MLS history, owner portfolio, distressors with dates, and scores. property_id is the id from search results.
Adding properties creates property records in your account and consumes property usage credits. Always quote first; quotes store and charge nothing.
| Method | Path | Body |
|---|---|---|
| POST | /properties/add-properties/quote/ | {"ids": ["102752166", ...]} |
| POST | /properties/add-properties/ | Same as above |
| POST | /properties/add-properties-by-query/quote/ | {"query": <search body>} |
| POST | /properties/add-properties-by-query/ | Same as above |
A quote tells you how many properties are already in your account, how many are new, and how many are billable:
{"total": 25, "in_account": 3, "new": 22, "already_fetched": 0, "billable": 22, "cost": null, "shortfall": null}For add-by-query, query.result_index and query.size bound which results are added. These endpoints return errors as {"success": false, "message": "...", "details": {"ids": ["This field is required."]}}.
After an add, records arrive in your account; verify with the DataSift API (for example the target list's properties-count).
A SiftMap filter is a saved nationwide search. With auto_add_enabled, the platform snapshots matching properties and feeds them into your account with your chosen lists and tags applied - a standing data feed defined entirely by API.
| Method | Path | Purpose |
|---|---|---|
| GET | /filters/ | List saved filters (offset, page_size, ordering, search, is_active) |
| POST | /filters/ | Create a filter |
| GET | /filters/{id}/ | Detail |
| PATCH | /filters/{id}/ | Update |
| DELETE | /filters/{id}/ | Delete |
| PATCH | /filters/{id}/favorite/ | Mark or unmark favorite ({"is_favorite": true}) |
| GET / PATCH | /filters/settings/ | Account-level filter settings |
Create payload fields: name (required), description, filter_data (required: {"filters": {...}, "addresses": [...]}, see the filter reference), is_active, auto_add_enabled, email_enabled, replace_owners_enabled, lists (list names to apply), tags (tag names to apply), limit plus limit_type (hourly, daily, weekly, monthly) to throttle how many records auto-add per period.
Creating or enabling an auto-add filter runs a matching-property count on the server and checks two things: the account has SiftMap Pro, and the count fits within the snapshot property cap. A too-broad filter is rejected with a validation error rather than silently truncated. While a snapshot job runs, filter_data updates are blocked and duplicate snapshot jobs are prevented.
- Create the filter with
auto_add_enabled: falseand the targetfilter_data. - Read it back and confirm
filter_datais stored as intended. - Set a conservative
limitandlimit_type. - PATCH
auto_add_enabled: true. A validation error here means the filter matches too many properties; tighten it. - Verify the feed: watch the target list's
properties-countin the DataSift API and spot-read a few arriving records.
POST /properties/grid/ returns property counts bucketed into a geotile grid, for drawing heatmaps. It takes the same addresses and filters as search plus precision (zoom level) and bounds (north, south, east, west).
SiftMap requests are subject to the limits described in Rate limits. The intended pattern is: search, drill into some property details, then add the properties you want. Pulling large volumes of property details without adding them to your account is not allowed. See Acceptable use.