12345Search -> find records matching your criteria | List -> save those record IDs as a named list (up to 1M records) | Export -> pull full data for the list whenever you need it
POST /v1/lists with your filters and locations. The response returns immediately with a list_id and status "building".1234567891011POST /v1/lists { "name": "High Value Properties in Miami", "source_type": "properties", "filters": [ { "filter_id": "estimated_value", "operator": "between", "min": 500000, "max": 2000000 } ], "locations": [ { "location_type": "city", "location_id": 12345 } ] }
record_ids to create a pre-populated list synchronously (max 250 IDs):123456POST /v1/lists { "name": "My Selected Properties", "source_type": "properties", "record_ids": [101, 202, 303] }
"completed" and total_count reflecting the number of records added.12345POST /v1/lists/:id/items { "ids": [101, 202, 303], "id_type": "internal_property_id" }
12345DELETE /v1/lists/:id/items { "ids": [101], "id_type": "internal_property_id" }
GET /v1/lists/:id until status is "completed".12345678910GET /v1/lists/abc-123 { "data": { "list_id": "abc-123", "status": "completed", "total_count": 45230, "progress": 100 } }
1234POST /v1/lists/abc-123/export { "fields": ["property_full_address", "estimated_value", "owner_full_name"] }
12345{ "locations": [], "include_lists": { "property_list_ids": [123] }, "exclude_lists": { "property_list_ids": [456] } }
people_list_ids for people lists. These fields use the Query Builder protocol; the API key's organization supplies the required organization and partition values automatically.| Constraint | Value |
| Max items per list | 1,000,000 |
| Max lists per account | Unlimited |
| List retention | Indefinite (until deleted) |
| Concurrent builds per org | 1 |