> ## Documentation Index
> Fetch the complete documentation index at: https://docs.captaindata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Updates

> New updates and improvements!

<Update label="May 28th, 2026" description="Find Company supports domain param">
  ### Find Company — domain param for better enrichment matching

  **Affected endpoint:** [Find Company](/v1/api/companies/find)

  CDv1 **“Find Company”** supports the **`domain`** param to improve match accuracy for enrichment use-cases. [Product request](https://www.notion.so/2e818c28ccb28056bf8cf0f26c41cc26)
</Update>

<Update label="April 1st, 2026" description="People Search — clearer errors">
  ### People Search — clearer errors about the source

  **Affected endpoint:** [People Search](/v1/api/people/search)

  Error responses from **People Search** are now **clearer about where the failure comes from**
</Update>

<Update label="March 20th, 2026" description="Sales Navigator pagination & cursor headers">
  ### Sales Navigator search — long queries and pagination headers

  **Pagination update:**\
  Legacy **`X-Pagination-Next`**/**`Previous`** headers (long URLs) are deprecated—migrate to **cursor-based pagination** (**`X-Cursor-Next`**/**`Previous`**). For long Sales Navigator queries, if URL headers are too larg (> 8Kb), the API now returns the cursor headers. Use whichever header is present for paging; cursor fallback is reliable and documented.
</Update>

<Update label="March 12th, 2026" description="Pricing display fixes">
  ### Pricing display fixes shipped

  We've shipped **pricing display fixes** impacting **plans**, **discounts**, and **totals** across the platform. You should now see consistent and correct pricing information wherever it is shown.

  ### API schema: headline deprecated, renamed to summary

  In the OpenAPI spec, the field **`headline`** has been renamed to **`summary`** in two schemas: **profile** and **person/employee-like** objects. **`headline`** is now **deprecated**; please use **`summary`** in new integrations.

  ### List endpoints: limit parameter maximum increased to 100

  The **`limit`** query parameter maximum has been increased from **20** to **100** (default remains 10) on the following list endpoints:

  * **[Get run callbacks](/v1/api/runs/callbacks)** — `GET /runs/callbacks`
  * **[List runs](/v1/api/runs)** — `GET /runs`
  * **[List schedules](/v1/api/schedules)** — `GET /schedules`
</Update>

<Update label="February 19th, 2026" description="Billing, MCP & error handling">
  ### Next billed amount reflects subscription discounts

  The **next billed amount** shown on the platform now includes any **discount applied to your subscription**, so you see the actual amount you'll be charged on the next invoice.

  ### MCP configuration examples — copy-paste ready

  We fixed the MCP (Model Context Protocol) configuration examples on the new Captain Data website so they are **copy-paste ready**. This reduces setup friction for customers exploring MCP usage.

  ### Improved error handling before returning to users

  We've reduced error risk by improving **internal error management** before errors are returned to the user. Errors are now processed and normalized internally first, leading to clearer and more consistent API responses.
</Update>

<Update label="January 28th, 2026" description="Find Company Employees filters & Find People error">
  ### Find Company Employees — Sales Navigator filter support

  **Affected endpoint:** [Find Company Employees](/v1/api/companies/find-employees)

  You can now reuse a **Sales Navigator People Search** (filters and keywords) and apply it to a company's employees. Pass the raw `query` parameter from a Sales Navigator people search URL to filter results (e.g. by current title, seniority, geography). The API merges these filters with the forced company context.

  See [Find Company Employees](/v1/api/companies/find-employees) for how to use the `query` parameter.

  ### Find People — Clear error when no unique result

  **Affected endpoint:** [Find People](/v1/api/people/find)

  When no unique result is found, the endpoint now returns a **clear and concise error** instead of an empty array. This makes it easier to distinguish "no match" from other issues and to handle the case explicitly in your integration.
</Update>

<Update label="January 15th, 2026" description="Cursor-based Pagination">
  ### Improved Pagination: Cursor-based

  **Affected endpoints:** All search endpoints ([People Search](/v1/api/people/search), [Companies Search](/v1/api/companies/search), [Find Company Employees](/v1/api/companies/find-employees))

  We've improved pagination across all search endpoints by transitioning to **cursor-based pagination**.

  **What's new:**

  * Pagination now uses the `cursor` parameter obtained from the `X-Pagination-Next` response header
  * Cursors are valid for **24 hours**, providing more flexibility for long-running integrations
  * More reliable and consistent results when paginating through large datasets

  **Breaking change:**

  * The `page` parameter has been **removed** — use cursor-based pagination instead

  **How to migrate:**

  1. Make your initial request without any pagination parameter
  2. Use the full URL from the `X-Pagination-Next` response header for subsequent requests
  3. Continue until `X-Pagination-Next` is no longer present

  See the updated [Pagination guide](/v1/pagination) for details.
</Update>

<Update label="January 9th, 2026" description="v3 Sunset & Bug Fix">
  ### 🌅 Captain Data v3 – End of Life

  Captain Data v3 has been officially sunset. All v3 features and endpoints are no longer available.

  We encourage all users to migrate to the [v1 API](/v1/introduction) for the latest capabilities and ongoing support.

  ### 🐛 Fix: Find People – Improved Profile Matching

  **Affected endpoint:** [`Find People`](/v1/api/people/find)

  We fixed an issue where the `Find People` endpoint could return non-unique or incorrect profiles. This update improves:

  * Deduplication of results
  * Accuracy of profile matching against your query
  * Overall result quality and reliability

  The endpoint now correctly returns only unique and relevant profiles matching your query.
</Update>

<Update label="v1.0 is here!" description="v1.0 – Public Release">
  ### 🚀 New Captain Data v1 – Official Public Release

  The new Captain Data is finally here! It makes it easy to get qualified, fresh and high-quality data about people and companies.

  You can now sign-up and start your journey on [https://app.captaindata.com](https://app.captaindata.com), following the simple [API documentation](/v1/introduction).

  You'll be able to:

  * Get enriched data about [people](/v1/api/people/enrich) and [companies](/v1/api/companies/enrich)
  * Find [people](/v1/api/people/find) and [companies](/v1/api/companies/find) based on generic informations
  * Search for [people (leads)](/v1/api/people/search) and [companies (accounts)](/v1/api/companies/search) based on Sales Navigator compatible queries
</Update>

<Update label="Planned for October 15th" description="v1.0 – Public Release">
  ### 🚀 New Captain Data v1 – Public Release

  The new Captain Data will be publicly available on October 15th and will make it easy to get qualified, fresh and high-quality data about people and companies.

  Get ready to get started at [https://app.captaindata.com](https://app.captaindata.com), following the simple [API documentation](/v1/introduction).
</Update>