Users correspond to other investors using the platform. Use data typically contains a short bio, investor’s primary location of operation, their specialties/skills as well as other locations/markets they operate in.
These endpoints fetch data related to current user or other visible users.
Fetch list of all visible users.
Fetch information for a specific user.
Update user information (your changes will be rejected unless you are logged in as the same user).
Fetch all blog post comments by this user.
Fetch all markers that belong to this user.
Markers can be thought of as personal vaults of data tied to a location. Each marker is owned by a user and by default not visible to other users (this setting can be changed by the owner). Markers are typically used to group a collection of research data related to a property under one umbrella, including research data, important events (such as bill due date or an open-house showing), documents, notes, credit card data, and even analytics gathered by our platform.
Marker API is used to interact with markers (tagged geolocations) owned by the user. Markers can have descriptions, analysis, and events attached to them.
Fetch list of all markers that belong to the logged-in user.
Fetch information for a specific marker.
Create a new marker that belongs to the logged-in user.
Update marker information (your changes will be rejected unless you are logged in as the user who owns this marker).
Delete the marker (your request will be rejected unless you are logged in as the user who owns this marker).
Fetch all events that belong to a given marker.
Events are typically tied to a marker, and generate a text/email notification at user’s request.
Events can be accessed independently of the markers they were attached to. This is useful for accessing them via a calendar.
Fetch list of all events attached to markers that belong to the logged-in user.
Fetch information for a specific event.
Create a new event that belongs to the logged-in user (you will need to specify the marker to attach the event to).
Update event information (your changes will be rejected unless you are logged in as the user who owns this event).
Delete the event (your request will be rejected unless you are logged in as the user who owns this event).