Investor Filters and Vocabulary

Introduction

This endpoint returns the machine-readable vocabulary for querying investors: the filter fields you can send to POST /investors, each field's data type and supported operators, the valid sort keys, and the sub-resources available on an individual investor.

Use it to discover what you can filter and sort by before building a request, or to drive a dynamic filter UI without hard-coding field names.

It takes no parameters and returns the same payload on every call.

Set up

Endpoint

GET https://multiples.vc/api/private/v1/lookup/investors

Request

This is a discovery endpoint. It accepts no path or query parameters and no request body - just send the Authorization header.

GET https://multiples.vc/api/private/v1/lookup/investors

The response describes each filter you may pass to POST /investors. The shape of every entry in filters:

field	type	description
`field`	string	The filter key to send under `filters` in a `POST /investors` request body.
`type`	string	Data type of the value: one of `string`, `number`, `boolean`, `date`, `datetime`, `uuid`, `array_string`, `array_uuid`.
`operators`	string[]	Comparisons supported for this field: any of `eq`, `in`, `gte`, `lte`, `between`, `overlaps`, `ilike`.
`description`	string	Optional. Human-readable note clarifying how to use the field. Present on some fields only.
`values`	string[]	Optional. Present only when the field is enum-backed - the closed set of accepted values. No investor filter is currently enum-backed, so this key is absent from every entry below.

Once you know the vocabulary, use it against the investor list endpoint. A minimal "all investors" call sends an empty filter set

{ 
  "limit": 100 
}

A filtered call uses the fields and operators reported by this lookup - here, US investors whose name contains "capital", sorted by name:

{
  "filters": {
    "country": ["USA"],
    "name": "capital"
  },
  "sort": "name:asc",
  "limit": 100
}

Response

{
  "data": {
    "filters": [
      {
        "field": "id",
        "type": "array_uuid",
        "operators": [
          "in"
        ]
      },
      {
        "field": "name",
        "type": "string",
        "operators": [
          "ilike",
          "eq"
        ]
      },
      {
        "field": "country",
        "type": "array_string",
        "operators": [
          "in"
        ],
        "description": "ISO-3 country codes."
      },
      {
        "field": "updated_at",
        "type": "datetime",
        "operators": [
          "gte"
        ],
        "description": "Change-feed checkpoint."
      },
      {
        "field": "include_deleted",
        "type": "boolean",
        "operators": [
          "eq"
        ],
        "description": "Default false. Set true on change-feed pulls."
      }
    ],
    "sort_fields": [
      "name",
      "updated_at"
    ],
    "sub_resources": [
      "/investors/{id}/investments",
      "/investors/{id}/co_investors",
      "/investors/{id}/portfolio"
    ]
  }
}

Fields

The payload is wrapped in the standard { "data": ... } envelope. This endpoint returns the discovery document only - there is no meta block.

field	type	description
`filters`	object[]	The filter fields accepted by `POST /investors`. Each entry has `field`, `type`, `operators`, and optionally `description` and `values` (see the request table above).
`sort_fields`	string[]	Field names valid in a `sort` clause (e.g. `name:asc`).
`sub_resources`	string[]	Path templates for per-investor sub-resources, with `{id}` standing in for an investor id.

Filters reported for investors:

field	type	operators	description
`id`	array_uuid	`in`	Match one or more investors by id.
`name`	string	`ilike`, `eq`	Investor name. Use `ilike` for partial, case-insensitive substring matches; `eq` for an exact match.
`country`	array_string	`in`	ISO-3 country codes (e.g. `USA`, `GBR`, `DEU`).
`updated_at`	datetime	`gte`	Change-feed checkpoint - return only investors changed at or after this timestamp.
`include_deleted`	boolean	`eq`	Default `false`. Set `true` on change-feed pulls to include soft-deleted records.

Sub-resources available per investor ({id} is the investor id):

path	description
`/investors/{id}/investments`	Funding rounds and deals the investor has participated in.
`/investors/{id}/co_investors`	Other investors that have appeared alongside this investor in deals.
`/investors/{id}/portfolio`	Companies the investor has backed.

Investor Filters and Vocabulary

Introduction

Set up

On this page