Skip to main content
The API serves the address of each property, with one exception. A property that a wholesaler lists on Investorlift now has no street address in a response. The rule applies to each route, each MCP tool, each CSV export and each key.

​
Why

A listing on Investorlift is the work of a wholesaler. A buyer who reads the street address can go to the seller and leave the wholesaler out. The Investorlift application shows the address after the buyer signs an agreement with the wholesaler. The API does not show it.

​
What a listed property serves

For each other property, address_held_back is null and location_radius_m is null.

​
Draw the approximate location

Draw a circle around latitude and longitude with a radius of location_radius_m metres. The circle always contains the true location. One property has one approximate point on each route, so a pin does not move between two responses.
Do not draw an exact pin for a row that has a location_radius_m. The point is not the house.

​
A search around a listed property

A request can name a listed property as its centre, with property_id or with address. The API measures each distance from the true location, so distance_miles is correct. The response does not give the true centre: meta.reference_point and meta.geometry give the approximate point, meta.geometry.address is null, and meta.geometry.location_radius_m gives the radius.

​
When the address comes back

The address comes back when the deed records show a transfer of the property after the listing. It also comes back when the listing has a recorded closing. A listing that ended with no sale keeps its address held back, because the records show no transfer.

​
In the MCP tools

The concise format carries address_held_back and location_radius_m only while they have a value. The detailed format carries them on each row.