For the complete documentation index, see llms.txt. This page is also available as Markdown.

People

👤 People API

Search for people and retrieve their associated interview transcripts.

Get People

get

Get people with their associated transcripts.

Supports filtering by:

  • name: partial match on person name
  • title: partial match on person title
  • company_id: only people linked to a specific company
  • company_name: only people linked to a company by name

Each result includes the person's basic info and all their published transcripts with call date, post date, call type, and associated companies.

Query parameters
namestring · nullableOptional

Search by person name (partial, case-insensitive)

titlestring · nullableOptional

Search by person title (partial, case-insensitive)

company_idstring · uuid · nullableOptional

Filter by associated company ID

company_namestring · nullableOptional

Search by associated company name (partial, case-insensitive)

orderingstring · nullableOptional

Order results by field. Use '-' prefix for descending (e.g., 'name', '-name')

pageinteger · min: 1Optional

Page number (starts from 1)

Default: 1
per_pageinteger · min: 1 · max: 100Optional

Number of items per page (max 100)

Default: 20
Header parameters
x-api-keystring · nullableOptional
Responses
200

Successful Response

application/json
get/api/v1/people
GET /api/v1/people HTTP/1.1
Accept: */*
{
  "data": [
    {
      "person_id": "123e4567-e89b-12d3-a456-426614174000",
      "full_name": "text",
      "title": "text",
      "bio": "text",
      "transcripts": [
        {
          "transcript_id": "123e4567-e89b-12d3-a456-426614174000",
          "call_date": "2026-01-01",
          "post_date": "2026-01-01",
          "project_affiliation": "text",
          "call_type": "text",
          "companies": [
            {
              "company_id": "123e4567-e89b-12d3-a456-426614174000",
              "company_name": "text",
              "stock_ticker": "text",
              "exchange": "text",
              "isin": "text"
            }
          ]
        }
      ]
    }
  ],
  "pagination": {
    "current_page": 1,
    "per_page": 1,
    "total_items": 1,
    "total_pages": 1,
    "has_next": true,
    "has_previous": true,
    "next_page": 1,
    "previous_page": 1
  }
}

📝 Description

The people endpoint allows you to search for experts and professionals in the database and retrieve all their associated interview transcripts. This endpoint supports:

  • Pagination: Control the number of results with page and per_page parameters (max 100 per page)

  • Name Filtering: Partial, case-insensitive search on the person's full name

  • Title Filtering: Partial, case-insensitive search on the person's job title

  • Company Filtering: Filter people by company using either company_id or company_name

  • Ordering: Sort results by a field name, ascending or descending (e.g. name, -name)

Search Types

  • Name Search: "John" matches "John Smith", "JOHN DOE", etc.

  • Title Search: "CEO" matches all people with CEO in their title

  • Company Name Search: "Apple" returns all people linked to Apple-related companies

  • Company ID Search: Exact match on a known company UUID

Parameter Details

ordering Parameter

Use the field name for ascending order, or prefix with - for descending:

  • "name" — alphabetical A → Z

  • "-name" — alphabetical Z → A

Response Structure

Each item in data includes:

  • person_id: Unique UUID for the person

  • full_name: Full display name

  • title: Job title (nullable)

  • bio: Biography text (nullable)

  • transcripts: List of all published transcripts associated with this person, each containing:

    • transcript_id, call_date, post_date, call_type, project_affiliation

    • companies: List of companies associated with that transcript

The nested transcripts entries are summaries — they do not carry data_source_provider, so you cannot attribute a person's interviews to a dataset from this response alone. Fetch GET /interviews/{transcript_id} for the provider, the metadata and the Q&A content.

There is also no provider filter here; data_source_provider_ids is an /interviews parameter only. (The MCP search_people tool does accept data_provider_names — see MCP Server.)

Last updated