Changelog

​

July 6, 2026

​

investment-funds endpoints renamed to funds

Breaking With the settled taxonomy (investor is the firm), the fund-vehicle endpoints dropped the investment- prefix: the top-level collection /api/data/investment-funds → /api/data/funds, and the investor sub-resource /api/data/investors/{id}/investment-funds → /api/data/investors/{id}/funds. The old paths have been removed — update client paths accordingly. The response shape is unchanged. Affected endpoints

• GET /api/data/funds
• GET /api/data/investors/*/funds

---

​

July 2, 2026

​

Removed is_top_story from news articles

Breaking The legacy is_top_story field has been removed from news article responses, along with the is_top_story filter. In the notes-only news model every article is a curated note, so the flag was true for all rows and carried no signal — use importance_score (ranking, sort=-importance_score) and is_pinned (the single hero story) instead. Clients on the previous version keep receiving is_top_story: true until the sunset date, and is_top_story clauses in their filter parameter are ignored (eq:true never narrowed results; eq:false always returned an empty set). Affected endpoints

• GET /api/data/news

---

​

June 30, 2026

​

Investor monetary fields dropped the _usd suffix

Breaking On investor responses, exit_total_value_usd and portfolio_total_valuation_usd were renamed to exit_total_value and portfolio_total_valuation; their values are now in the response’s active currency (default USD) rather than always USD. Clients pinned to an earlier API-Version keep receiving the _usd field names until the sunset date. Affected endpoints

• GET /api/data/investors

​

Investment-fund amount now in the active currency; native value moved to amount_source

Breaking Investment-fund responses now return amount in the response’s active currency and expose the original stored value under amount_source ({ amount, currency }); the top-level native currency field was removed. Clients pinned to an earlier API-Version keep the previous shape — amount in the fund’s native currency plus a top-level currency — until the sunset date. Affected endpoints

• GET /api/data/investment-funds
• GET /api/data/investors

​

Nested company summary total_funding/latest_valuation dropped the _usd suffix

Breaking On funding-round (/api/data/transactions) and portfolio (/api/data/investors/{id}/portfolio) responses, the nested company.total_funding_usd / company.latest_valuation_usd fields were renamed to company.total_funding / company.latest_valuation and are now in the response’s active currency. Clients pinned to an earlier API-Version keep the _usd field names until the sunset date. Affected endpoints

• GET /api/data/investors
• GET /api/data/transactions

---

​

June 23, 2026

​

Entity changelog endpoint removed

Breaking The GET /api/data/entities/{id}/changelog endpoint and its ChangelogResponse schema have been removed, along with the updated, added, change_type, and changed_categories delta filters. Per-entity change history is no longer exposed via the API; delta detection is now an internal data-loader concern. Use the deleted filter for soft-delete tracking. Affected endpoints

• GET /api/data/entities/{id}/changelog

---

​

June 21, 2026

​

/entities/{id} relationship sub-resources moved to typed collections

Breaking The relationship sub-resources transactions, valuations, financials, investors, investments, investment-funds, and team have been removed from /api/data/entities/{id}. /entities/{id} now carries only the detail record and changelog. Each relationship lives on the typed collection whose facet owns it: company funding rounds at /api/data/companies/{id}/funding-rounds (plus valuations, financials, investors, team); investor portfolio and raised funds at /api/data/investors/{id}/portfolio and /investment-funds; and team additionally on /api/data/investors/{id}/team, /api/data/universities/{id}/team, and /api/data/gov-ngo/{id}/team. Read the entity’s type / organization_subtype / is_investor / is_founder flags from the detail payload and call the matching typed endpoint — the paths are static and knowable. New relationship sub-resources were also added: /api/data/people/{id}/career, /api/data/founders/{id}/founded-companies, and /api/data/universities/{id}/alumni. /api/data/entities/{id}/lp-funds is unchanged. Response shapes are unchanged; only the URL paths moved. Affected endpoints

• GET /api/data/entities/*/financials
• GET /api/data/entities/*/investment-funds
• GET /api/data/entities/*/investments
• GET /api/data/entities/*/investors
• GET /api/data/entities/*/team
• GET /api/data/entities/*/transactions
• GET /api/data/entities/*/valuations

---

​

June 19, 2026

​

Investor subtype renamed from fund to investor

Behavioral The organization_subtype value for investment firms is now investor (previously fund). The fund term now refers only to the investment vehicle, not the firm. Clients pinned to a version before 2026-06-19 keep receiving fund in responses. The organization_subtype filter now accepts only investor; fund is no longer a valid filter value. Affected endpoints

• GET /api/data/entities
• GET /api/data/investors

​

/entities/{id}/funds renamed to /entities/{id}/investment-funds

Breaking The entity sub-resource listing the investment vehicles a firm has raised moved from /api/data/entities/{id}/funds to /api/data/entities/{id}/investment-funds, matching the settled taxonomy where investment_fund is the vehicle. The old path has been removed — update client paths accordingly. The response shape is unchanged. Affected endpoints

• GET /api/data/entities/*/investment-funds

---

​

June 18, 2026

​

API key created_by may be null for orphaned keys

Breaking The created_by field on API key responses is now null when the user who created the key has been deleted (keys remain active but are no longer associated with a user). Clients on the previous version continue to receive an empty string for orphaned keys. Affected endpoints

• GET /api/platform/api-keys

---

​

June 17, 2026

​

API endpoints reorganized under functional namespaces

Breaking Every endpoint now lives under a functional namespace — /api/data/* (entities, transactions, valuations, investors, founders, people, news, jobs, search), /api/analytics/* (aggregate, funding-analytics, timeseries, matching), /api/reference/* (filters, landscapes), /api/platform/* (account, api-keys, teams, usage, ecosystems), and /api/system/* (health, metrics). The previous flat /api/<resource> paths have been removed — update client base paths accordingly. Request and response shapes are unchanged; only the URL prefix moved. Affected endpoints

• GET /api/analytics/
• GET /api/data/
• GET /api/platform/
• GET /api/reference/
• GET /api/system/

---

​

June 2, 2026

​

Removed legacy classification flags from entities

Breaking The deprecated is_company, is_university, is_crowdfunding, is_government, and is_non_profit flags have been removed from entity responses. Use organization_subtype (company / university / gov_ngo / fund) instead. Clients on the previous version keep receiving the flags, reconstructed from organization_subtype until the sunset date: is_company ⇐ company, is_university ⇐ university, is_government ⇐ gov_ngo. is_crowdfunding (now part of company) and is_non_profit (now part of gov_ngo) can no longer be distinguished and downgrade to false. Affected endpoints

• GET /api/data/companies
• GET /api/data/entities
• GET /api/data/gov-ngo
• GET /api/data/people
• GET /api/data/universities

---

​

May 29, 2026

​

Removed is_ai_summarised from news articles

Breaking The is_ai_summarised field has been removed from news article responses. The upstream data source no longer provides this signal. Clients on the previous version will continue to receive is_ai_summarised: false until the sunset date. Affected endpoints

• GET /api/data/news

---

​

May 25, 2026

​

Cursor (keyset) pagination

Addition List endpoints now support cursor (keyset) pagination alongside the existing ?limit= / ?offset= mode — both are first-class and no migration is required. Responses gain two new fields in the page envelope: next_cursor and prev_cursor, opaque tokens that can be round-tripped via ?cursor= to step through pages without paying the deep-offset scan cost. Every request — cursor-mode or offset-mode — gets minted cursor tokens back, so callers can switch to keyset at any point in a walk. When both ?cursor= and ?offset= are sent on the same request, the cursor wins and the offset is ignored. Existing ?limit=/?offset= requests continue to work unchanged and run classic SQL LIMIT/OFFSET. Clients pinned to an earlier API-Version see the previous { limit, offset, total } envelope unchanged — the new fields are stripped on the way out. Affected endpoints

• GET /api/data/companies
• GET /api/data/entities
• GET /api/data/founders
• GET /api/data/gov-ngo
• GET /api/data/investors
• GET /api/data/news
• GET /api/data/people
• GET /api/data/transactions
• GET /api/data/universities
• GET /api/data/valuations

​

Funding sort keys renamed to date

Breaking The funding-round sort keys year and month have been replaced by a single date key (backed by the funding_date_ym column). Affects GET /api/data/transactions. Clients pinned to an earlier API-Version will continue to work — requests with sort=-year, sort=-month, or sort=-year,-month are rewritten to sort=-date until the sunset date. Affected endpoints

• GET /api/data/transactions

​

When enabled, list endpoints use keyset SQL and expose next_cursor / prev_cursor in the response page envelope.

Behavioral When enabled, list endpoints use keyset SQL and expose next_cursor / prev_cursor in the response page envelope.

---

​

May 22, 2026

​

Monetary fields are integers, not strings

Breaking Monetary fields in responses (amount, valuation, total_funding, total_invested, latest_valuation.value, latest_revenue.value, founded_companies_total_funding, revenue, ebitda, etc.) are now JS numbers in whole units of the active currency. Previously they were strings like "85000000.00". Filter inputs for these fields now also reject fractional values — pass integers only. Affected endpoints

• GET /api/data/companies
• GET /api/data/entities
• GET /api/data/founders
• GET /api/data/gov-ngo
• GET /api/data/investors
• GET /api/data/news
• GET /api/data/people
• GET /api/data/transactions
• GET /api/data/universities
• GET /api/data/valuations

---

​

May 13, 2026

​

Removed null placeholder fields from entities and news articles

Breaking The fund object (containing fund_size_usd, vintage_year, is_raising, fund_status) has been removed from entity responses. The language, relevance_score, and hub_score fields have been removed from news article responses. These fields were placeholder columns that were always null in production and have been dropped from the database. Affected endpoints

• GET /api/data/companies
• GET /api/data/entities
• GET /api/data/founders
• GET /api/data/gov-ngo
• GET /api/data/investors
• GET /api/data/news
• GET /api/data/people
• GET /api/data/universities

---

​

April 10, 2026

​

Reverted short_description back to tagline

Breaking The short_description field has been renamed back to tagline on entity, investor, and founder responses. Clients on version 2026-04-02 will continue to receive short_description until the sunset date. Affected endpoints

• GET /api/data/entities
• GET /api/data/founders
• GET /api/data/investors

---

​

April 2, 2026

​

Renamed tagline to short_description

Breaking The tagline field has been renamed to short_description on entity, investor, and founder responses. Clients on version 2026-03-16 will continue to receive tagline until the sunset date. Affected endpoints

• GET /api/data/entities
• GET /api/data/founders
• GET /api/data/investors

---

​

March 16, 2026

Initial launch version. No breaking changes.

---