Skip to main content
GET
Get the full profile of one investor
Everything the API knows about one Investor: who they are, how they operate, how recently they bought, and how to contact them.

Use it when

The investor drawer, which you open from a list row, a deal row or a search hit. Also each time an id you stored earlier needs a refresh. For the investor’s deals, use GET /v1/investors/{id}/deals. To find an id from a name, use GET /v1/investors/search.

Read the response

  • The API returns person names SURNAME GIVEN, as on the deed. Print display_name (since 0.29.0). It is the same person given-first when the spelling parsed cleanly, and it equals name otherwise. For a member, use the split fields given and surname, never a given-first splitter on name. If is_ambiguous is true, the split is unsafe: show the raw name.
  • contact.mailing_addresses lists every address. is_generic marks title companies, registered agents and shared head offices. contact.primary_address is the best non-generic one, usually where the investor actually is. skip_trace_targets pairs a person with an address, best first. Read it as: send these to a skip-trace vendor in this order.
  • The API measures days_since_last_purchase and every _12m / _24m window from data_end, never from today.
  • median_purchase_year (since 0.26.0) is the median year the investor bought what it still holds. It is null when no holding has a date to measure: The Investor object. The lists filter on the same count (holds_min and holds_max). GET /v1/investors sorts on the holdings inside a geometry (sort=holds_desc).
  • buyer_signal is the operator behind this investor: the ids it spans, where it is in its capital cycle, and its fitted probability to buy again. The API serves it to every key, ids and numbers only. See Same buyer, cash right now.
  • financing (since 0.16.0) is what the lender registry ties to the investor. It carries the loans, which the API counts once across the open-lien and recorded-history tables, the lenders behind them and the last loan. It says for how many of the recent purchases the registry found a loan, and if a hard-money lender was among them. The API serves it to every key, because lender names are business records. It is null in a market without a published registry or borrower match. Every count is a floor of a partial feed: The Investor object.
  • meta.resolved_from is present when a refresh replaced the id you sent with a newer one. Store the new id.

Gotchas

  • This host does not serve members, contact.primary_address, contact.mailing_addresses, contact.person_members and contact.skip_trace_targets (null, contact_redacted: true). This host serves member_names, but it lists only the entity and trust names.
  • For a retired id, the API answers 410 gone with superseded_by: null. Search by name instead. A merged id is not an error: you get the new profile with meta.resolved_from. For an id that the API never issued, the API answers a 404.
  • Public bodies and institutional investors resolve here even though the lists hide them. The route does not accept include_public and answers 400 unknown_parameter: the API always returns a profile reached by id.
  • Pass market when an id exists in more than one loaded market. 400 market_required says so and lists them.
Tell me about this investor.

Authorizations

Authorization
string
header
required

API key from the developer console (starts with zpka_). Create one at https://developers.investorlift.com/get-a-key.

Path Parameters

id
string
required

Investor id, inv_ followed by 12 hex characters, for example inv_abaf618f44a3. The API follows an old id from an earlier data refresh to the current investor (meta.resolved_from). It answers 410 for a retired id.

Query Parameters

market
string

Market code, for example phx. The loaded markets are in meta.coverage[]. Send it only when the id exists in more than one loaded market. 400 market_required says so. Otherwise the API uses the id's own market.

Required string length: 1 - 16

Response

The full profile. meta.resolved_from lists the old ids that redirected here.

The full profile. meta.resolved_from lists the old ids that redirected here.

data
object
required

The full profile of one investor: identity, activity, price band, buyer signal and listings. It also carries the linked listing agents, Investorlift purchases, short-term rental holdings, financing and id history.

meta
object
required

Response metadata: when the API produced it, which markets it covers, and how fresh they are.