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

# Changelog

> New endpoints, fields and behaviour changes in the Specter API — newest first.

New endpoints, fields and behaviour changes in the Specter API — newest first. Use the tags to filter by product.

Bookmark this page for updates. If an update isn't clear or you need help planning a migration, email [api-support@tryspecter.com](mailto:api-support@tryspecter.com).

<Update label="2026-07-14" description="v0.1.0" tags={["Revenue Signals", "News Signals", "Talent Signals", "Investor Interest", "Investors"]}>
  New filters:

  The following endpoints now accept explicit date-range query parameters, named
  after the date each object is keyed on. Both bounds are inclusive of the given
  calendar day (`YYYY-MM-DD`) and can be combined:

  * [List Revenue Signals](/api-reference/revenue-signals/list-revenue-signals), [Get Revenue Signals for a company](/api-reference/revenue-signals/get-revenue-signals-for-a-company) and [Get Revenue Signals for a saved company search](/api-reference/revenue-signals/get-revenue-signals-for-a-saved-company-search) — `revenue_signal_date_after` / `revenue_signal_date_before`. When both `new` and `revenue_signal_date_after` are given, the explicit date wins.
  * [Get News Signals for a company](/api-reference/news-signals/get-news-signals-for-a-company) and [Get News Signals for a saved company search](/api-reference/news-signals/get-news-signals-for-a-saved-company-search) — `news_publication_date_after` / `news_publication_date_before`.
  * [Get Talent Signals saved search results](/api-reference/talent-signals-saved-searches/get-talent-signals-saved-search-results) — `talent_signal_date_after` / `talent_signal_date_before`.
  * [Get Investor Interest Signals saved search results](/api-reference/investor-interest-saved-searches/get-investor-interest-signals-saved-search-results) — `investor_signal_date_after` / `investor_signal_date_before`.
  * [Get investor funding rounds](/api-reference/investors/get-investor-funding-rounds) — `funding_announced_date_after` / `funding_announced_date_before`.
</Update>

<Update label="2026-07-10" description="v0.1.0" tags={["AI Search"]}>
  New endpoints:

  **AI Search**

  [AI Search](/api-reference/ai-search/ai-search) turns a natural-language query into a structured search across all products and returns matching records. Set `resource_type` to target a specific product, or leave it empty to let the API infer it. Results use the same format as other endpoints and support `page`/`limit` pagination.

  Costs 1 credit per result — use `limit=1` to check `total_count` before fetching more. User-scoped filters (network, CRM, saved lists) aren't supported and will return a `422` error.
</Update>

<Update label="2026-07-09" description="v0.1.0" tags={["Companies", "Revenue Signals"]}>
  New endpoints:

  **Companies**

  * [Resolve company ID](/api-reference/companies/resolve-company-id) — resolves a batch of alternate identifiers (domain, website, LinkedIn URL, or company name) into the Specter company `id`, so you can then call the id-only company endpoints (revenue, valuation, people, …) without knowing the Specter ID upfront. Send up to 50 identifiers under `to_resolve` and get one result group per input, in order. Exact identifiers return a single match; a name is fuzzy-matched and returns up to 10 ranked candidates. Free — no credits are charged.
  * [Get company competitors](/api-reference/companies/get-company-competitors) — returns the competitive landscape for a company: a ranked list of competitors, the dimensions the market splits on, and a summary of the landscape. The optional request body accepts `limit` (1–30, default 30) and `refresh` (default `false`). It's cache-first — an already-analysed company returns instantly, while a cold company (or `refresh: true`) computes the landscape on demand; results older than 30 days are recomputed automatically, and `last_updated` reports when it was last computed. Costs 1 credit per request.

  **Revenue Signals**

  * [Get Revenue Signals for a company](/api-reference/revenue-signals/get-revenue-signals-for-a-company) — returns a single company's full revenue (and profitability) signal history in reverse chronological order (most recent first), identified by its Specter company ID. Supports `limit`/`page` pagination and a `new` toggle that restricts results to signals published in the current week. Returns `404` when the company is unknown; a known company with no signals returns a 200 with an empty array. Costs 10 credits per signal returned.
</Update>

<Update label="2026-07-01" description="v0.1.0" tags={["Companies"]}>
  Removed fields:

  **Company response**

  * `revenue_estimate_usd` has been removed from the company object. This field carried an estimated annual revenue band that was almost always `null`, and is no longer returned by any endpoint that includes a company.

  **What you need to do:** if your integration reads `company.revenue_estimate_usd`, stop relying on it.
</Update>

<Update label="2026-06-30" description="v0.1.0" tags={["Companies"]}>
  New endpoints:

  **Companies**

  * [Get Latest Revenue for a Company](/api-reference/companies/get-latest-revenue-for-a-company) — returns the latest revenue figures and estimated revenue growth for a single company, by Specter company ID. Includes the estimated and last-reported revenue (with its reported metric type) plus estimated revenue growth across 1-month to 2-year windows. Costs 1 credit per request.
  * [Get Latest Valuation for a Company](/api-reference/companies/get-latest-valuation-for-a-company) — returns the latest valuation figures and estimated valuation growth for a single company, by Specter company ID. Includes the estimated and last-reported post-money valuation plus estimated valuation growth across 1-month to 2-year windows. Costs 1 credit per request.
</Update>

<Update label="2026-06-12" description="v0.1.0" tags={["Revenue Signals"]}>
  New endpoints:

  **Revenue Signals**

  * [Get Revenue Signal by ID](/api-reference/revenue-signals/get-revenue-signal-by-id) — retrieve a single revenue (or profitability) signal by its Specter signal id (`rev_...`). Each signal corresponds to one observation derived from news coverage or a public filing — the revenue (or profitability) figures, the year they refer to, the source URL, and the company they are attributed to.
  * [List Revenue Signals](/api-reference/revenue-signals/list-revenue-signals) — list revenue (and profitability) signals, newest first. Each item is the same signal object returned by [Get Revenue Signal by ID](/api-reference/revenue-signals/get-revenue-signal-by-id).
  * [Get Revenue Signals for a company list](/api-reference/revenue-signals/get-revenue-signals-for-a-company-list) — returns every revenue signal attributed to the companies in a given list, newest first. Companies outside the list are excluded. Lists with more than 5,000 member companies are capped at that limit; unknown or non-visible lists return `404`.
  * [Get Revenue Signals for a saved company search](/api-reference/revenue-signals/get-revenue-signals-for-a-saved-company-search) — returns every revenue signal attributed to the companies returned by a saved company search, newest first. Date-range queries live inside the saved search itself. Searches matching more than 5,000 companies are capped at that limit; unknown or non-visible searches return `404`.

  Behavior common to both:

  * `new=true` restricts the results to signals published in the current week.
  * Supports `limit`/`page` pagination.
  * These endpoints use 10 credits per signal returned.
</Update>

<Update label="2026-06-11" description="v0.1.0" tags={["Platform"]}>
  **Credit-limit responses now return 402**

  Running out of credits now returns HTTP `402` instead of HTTP `429`, so you can distinguish being credit‑limited from being rate‑limited:

  * `402` with errorCode `OUT_OF_CREDITS` — your team has no credits left for the current billing period. The response carries the `X-CreditLimit-*` headers, including `X-CreditLimit-Reset` with the seconds until credits renew.
  * `429` with errorCode `RATE_LIMITED` — unchanged; you sent too many requests per second.

  **What you need to do:** if your integration treats `429` as "out of credits", update it to handle `402` for that case. Retry-on-429 logic can stay as is.
</Update>

<Update label="2026-06-09" description="v0.1.0" tags={["Enrichment", "Companies", "Investors", "Talent Signals", "Interest Signals"]}>
  **Bulk Endpoints**

  New endpoints — bulk variants of the existing lookup and enrichment endpoints. Each accepts up to 50 identifiers in a single request, so you can resolve many records in one call instead of issuing them one at a time. For lookup endpoints, unknown identifiers are silently omitted; for enrichment endpoints each row carries a found/queued status (see the entry). Each uses 1 credit per record returned (misses/queued rows are not charged).

  **Enrichment**

  * [Bulk enrich companies by ID](/api-reference/enrichment/bulk-enrich-companies-by-id) — bulk counterpart to [Enrich companies](/api-reference/enrichment/enrich-companies); resolve companies by website, domain, LinkedIn URL/ID, or Crunchbase URL. Each row carries a status of found (with the company payload) or queued (an enrichment was started for an unknown company); only found rows are charged.
  * [Bulk enrich people by ID](/api-reference/enrichment/bulk-enrich-people-by-id) — bulk counterpart to [Enrich people](/api-reference/enrichment/enrich-people); resolve people by LinkedIn URL/ID/URN. Each row carries a status of found (with the person payload) or queued (async enrichment started); only found rows are charged.
  * [Bulk reverse email lookup](/api-reference/enrichment/bulk-reverse-email-lookup) — bulk counterpart to [Reverse email lookup](/api-reference/enrichment/reverse-email-lookup); reverse-lookup people from email addresses.

  **Companies**

  * [Bulk get similar companies by ID](/api-reference/companies/bulk-get-similar-companies-by-id) — bulk counterpart to [Get similar companies](/api-reference/companies/get-similar-companies); find lookalike companies for multiple seed company IDs at once.

  **Investors**

  * [Bulk get investors by ID](/api-reference/investors/bulk-get-investors-by-id) — look up investors by website or name.

  **Talent and Interest Signals**

  * [Bulk get Talent Signals by ID](/api-reference/talent-and-interest-signals/bulk-get-talent-signals-by-id) — bulk counterpart to [Get Talent Signal](/api-reference/talent-and-interest-signals/get-talent-signal-by-id); fetch talent signals by ID. Duplicate IDs are honored.
  * [Bulk get Investor Interest Signals by ID](/api-reference/talent-and-interest-signals/bulk-get-investor-interest-signals-by-id) — bulk counterpart to [Get Investor Interest Signal by ID](/api-reference/talent-and-interest-signals/get-investor-interest-signal-by-id); fetch investor interest signals by ID. Duplicate IDs are honored.
</Update>

<Update label="2026-06-08" description="v0.1.0" tags={["Companies", "People", "Investors"]}>
  **Name based search for companies, people and investors**

  Name-based search across companies, people and investors. Each search endpoint takes a required `query` string (minimum 3 characters), returns up to 10 lightweight results sorted by descending `match_confidence`, and uses 1 credit per request regardless of how many matches come back. Chain the corresponding `GET /{id}` endpoint on any result for the full profile.

  **People search**

  * [Search person name](/api-reference/people/search-person-name) — fuzzy search for people by name. Returns up to 10 candidates, each with `id`, `full_name`, `headline`, `linkedin_url`, `profile_picture_url`, `current_company_name`, and a `match_confidence`. Only matches scoring at least 0.5 are returned; no match returns an empty list. This is a catalogue search and never triggers enrichment — to enrich a brand new LinkedIn identifier, keep using [Enrich people](/api-reference/enrichment/enrich-people).

  **Investor search**

  * [Search investor name](/api-reference/investors/search-investor-name) — fuzzy search for investors by name. Returns up to 10 candidates, each with `id`, `name`, `domain`, `hq_location`, `founded_year`, `type`, and a `match_confidence`. Only matches scoring at least 0.5 are returned. [Look up investors](/api-reference/investors/look-up-investors) (lookup by website / exact name) is unchanged.

  **Company search**

  * [Search company name](/api-reference/companies/search-company-name) now returns a `match_confidence` on every result and applies the same 0.5 threshold, so weak matches no longer appear.

  **A note on match\_confidence**

  All three endpoints expose `match_confidence` on a 0–1 scale, but they are derived differently. Investor search uses trigram similarity, which is absolute — scores are comparable across separate calls. People and company search scores are relative to the results within a single response and should not be compared between calls.
</Update>

<Update label="2026-06-05" description="v0.1.0" tags={["Network Mapping"]}>
  New endpoints:

  **Network Mapping**

  Three new endpoints expose your team's LinkedIn network — the people your teammates are connected to, deduped across the team, and the companies they work at. Use them to find a warm path into a target company or to surface who on your team already knows a given contact.

  * [Get people in your team's network](/api-reference/network/get-people-in-your-teams-network) — returns all people your team is connected to on LinkedIn, deduped across teammates. Each result includes which teammates hold the connection. Supports `limit`/`page` pagination and a `connected_on` filter (only `linkedin` is supported today).
  * [Get companies in your team's network](/api-reference/network/get-companies-in-your-teams-network) — returns all companies where someone in your team's network currently works, ordered by number of connections at each company. Each result includes the person IDs of your contacts there. Supports `limit`/`page` pagination and a `min_connections` filter to only return companies with at least that many network contacts.
  * [Get your team's network at a company](/api-reference/network/get-your-teams-network-at-a-company) — returns your team's connections at a specific company: who you know there, what roles they hold, and which teammates are linked to them. Returns `404` when your team has no connections at the requested company.

  Each endpoint uses 1 credit per request.

  **Organization**

  * [List your team's members](/api-reference/organization/list-your-teams-members) — returns all active members of your team: their user ID, role (admin or member), name, and email. Suspended users are excluded. Supports `limit`/`page` pagination. The `user_id` field matches the `connected_teammates` values returned by the Network endpoints, so you can use it to resolve teammate IDs back to a named person. This endpoint uses 1 credit per request.
</Update>

<Update label="2026-05-22" description="v0.1.0" tags={["News Signals"]}>
  New endpoints:

  **News Signals**

  * [Get News Signal by ID](/api-reference/news-signals/get-news-signal-by-id) — retrieve a single news signal by its integer Specter signal id. A news signal represents one classified company mention within a single article; when an article mentions multiple companies, each company yields its own signal.
  * [Get News Signals for a company](/api-reference/news-signals/get-news-signals-for-a-company) — returns a company's full news signal history in reverse chronological order (most recent first). Supports `limit`/`page` pagination and a `major_only` toggle that restricts results to signals with importance score ≥ 4.

  Each signal includes the underlying article (id, URL, title, published date, featured image), the kinds of `meaningful_updates` detected (revenue, profitability, traction, funding, deals), an AI-generated summary of what's new, and an importance score on a 0–5 scale.
</Update>

<Update label="2026-05-20" description="v0.1.0" tags={["Investors"]}>
  New endpoints:

  **Investor lookup**

  * [Look up investors](/api-reference/investors/look-up-investors) — look up Specter investor records by `website` and/or `name` query parameters. Returns the matching investor records with full detail (profile, activity, targeting, funds, portfolio companies). Use it to resolve an inbound mention of an investor — a domain on a deck, a firm name in a press release — to the canonical Specter ID for downstream calls.

  Behavior:

  * The endpoint returns a list of investors. A lookup can match more than one investor (e.g. multiple firms sharing a domain), so the endpoint returns all matches.
  * When no investor matches, the response is `404 Not Found`.
  * Query parameters: provide at least one of `website` or `name`. Supplying both narrows the match. Missing both returns `422`.
</Update>

<Update label="2026-05-19" description="v0.1.0" tags={["Investors", "Lists", "Saved Searches", "Transactions"]}>
  New endpoints:

  **Investors**

  * [Get investor by ID](/api-reference/investors/get-investor-by-id) — returns the full Specter investor record for a single investor ID, including profile, targeting, funds, and portfolio companies. Useful for enriching a known investor, pulling portfolio company IDs for downstream calls, or inspecting targeting (industries, verticals, stages) before outreach.

  **Investor saved searches**

  * [Get investor saved search details](/api-reference/investor-saved-searches/get-investor-saved-search-details) — returns the name, query ID, and total matched-investor count for a saved investor search. Use it to confirm a search is bound to the expected query, or to surface counts in a UI without fetching results.
  * [Get investor saved search results](/api-reference/investor-saved-searches/get-investor-saved-search-results) — returns the investors matching a saved investor search with full detail (profile, activity, targeting, funds, portfolio companies). Supports `limit` (default 50, max 5000) and `page` (0-indexed).

  **Investor lists**

  * [Get all investor lists](/api-reference/investor-lists/get-all-investor-lists) — returns all investor lists created with the API, shared with the API, or shared globally, including the count of investors in each list.
  * [Create a new investor list](/api-reference/investor-lists/create-a-new-investor-list) — create a new investor list.
  * [Get specific investor list info](/api-reference/investor-lists/get-specific-investor-list-info) — retrieve details of a specific investor list, including the investor IDs it contains.
  * [Modify an investor list](/api-reference/investor-lists/modify-an-investor-list) — modify an existing investor list.
  * [Delete an investor list](/api-reference/investor-lists/delete-an-investor-list) — delete an investor list.
  * [Get investor list results](/api-reference/investor-lists/get-investor-list-results) — returns the investors in a specific list along with their current profile, activity, and targeting data. The list must be of product type investors and must be shared with the API or created by the API.

  **Transactions**

  Three new typed resources cover the company-level transaction history — funding rounds, acquisitions, and IPOs — that used to require bulk delivery. Use these to look up a transaction referenced from another API response, audit an investor's recent activity, or stitch a company's funding history into your CRM without round-tripping through bulk exports.

  Funding rounds:

  * [Get funding round by ID](/api-reference/transactions/get-funding-round-by-id) — a single round with its raising company and full investor list (lead flagged).
  * [Get company funding rounds](/api-reference/companies/get-company-funding-rounds) — paginated funding history for one company.
  * [Get investor funding rounds](/api-reference/investors/get-investor-funding-rounds) — paginated list of rounds an investor has participated in.

  Acquisitions:

  * [Get acquisition by ID](/api-reference/transactions/get-acquisition-by-id) — a single acquisition with acquirer and acquiree context.
  * [Get company acquisitions](/api-reference/companies/get-company-acquisitions) — acquisitions where the given company is the acquirer.

  IPOs:

  * [Get IPO by ID](/api-reference/transactions/get-ipo-by-id) — a single IPO with the issuing company, exchange and ticker symbol, listing date, and proceeds in USD.
  * [Get company IPOs](/api-reference/companies/get-company-ipos) — IPOs by company.
</Update>

<Update label="2026-04-20" description="v0.1.0" tags={["Platform"]}>
  New endpoints:

  **API Call Logs**

  * [List API call logs](/api-reference/customer-data/list-api-call-logs) — returns a paginated list of API calls made by your organization, ordered by most recent first. Use it to audit which endpoints your integration is hitting, debug failed calls by inspecting HTTP status codes and paths, and monitor usage trends across your team.

  Parameters:

  * `limit` / `page` — pagination controls
  * `from` / `to` — date range filter for log entries

  Response fields per entry:

  * `timestamp` — UTC timestamp of the call
  * `path` — request path (e.g. `/v1/companies`)
  * `url` — full URL including query string
  * `http_method` — HTTP verb used
  * `http_status` — HTTP status code returned
  * `status` — logical status (`ok` or `error`)
  * `query` — query parameters sent with the request (nullable)
</Update>

<Update label="2026-04-09" description="v0.1.0" tags={["Talent Signals", "Interest Signals"]}>
  New parameters:

  **Talent search results & Investor Interest search results**

  Both endpoints now accept a `new` query parameter (boolean, default false). When set to true, results are restricted to signals from the current week, overriding any `SignalDate` filter that is stored in the saved search. This is equivalent to applying a "This week" signal date filter without modifying the saved search itself — useful for polling integrations that always want the latest batch of signals.

  Affected endpoints:

  * [Get Talent Signals saved search results](/api-reference/talent-signals-saved-searches/get-talent-signals-saved-search-results)
  * [Get Investor Interest Signals saved search results](/api-reference/investor-interest-saved-searches/get-investor-interest-signals-saved-search-results)
</Update>

<Update label="2026-03-20" description="v0.1.0" tags={["Companies", "Talent Signals", "Interest Signals"]}>
  New fields:

  **Company response**

  * Pitchbook URL — `company.socials.pitchbook.url`
  * Crunchbase URL — `company.socials.crunchbase.url`
  * HQ regions — `company.hq.regions`
  * HQ continent — `company.hq.continent`
  * Glassdoor data — `company.glassdoor`
  * Glassdoor rating metrics — `company.traction_metrics.glassdoor_rating`
  * Glassdoor reviews metrics — `company.traction_metrics.glassdoor_reviews`

  **Talent response**

  * Signal Summary — `talent.signal_summary`
  * Experience Industry — `talent.experience[].industry`
  * Experience Tech Verticals — `talent.experience[].tech_verticals`
  * New position industry — `talent.new_position_industry`
  * New position tech verticals — `talent.new_position_tech_verticals`
  * Is new position industry estimated — `talent.is_new_position_industry_estimated`

  **Investor Interest response**

  * Signal Summary — `investor_interest.signal_summary`
  * Person Industry — `investor_interest.person.industry`
  * Person Tech Verticals — `investor_interest.person.tech_verticals`
  * Person Is industry estimated — `investor_interest.person.is_industry_estimated`
  * Company Industry — `investor_interest.company.industry`
  * Company Tech Verticals — `investor_interest.company.tech_verticals`
  * Company Is industry estimated — `investor_interest.company.is_industry_estimated`
  * Company Customer Focus — `investor_interest.company.customer_focus`

  Deprecated fields:

  **Company response**

  * HQ region — move to `company.hq.continent`.
</Update>

<Update label="2025-11-20" description="v0.1.0" tags={["People", "Enrichment"]}>
  Features:

  **Enrich/Get Person**

  * People can now be retrieved via the `linkedin_num_id` and the `linkedin_urn`.

  New fields:

  **Person responses**

  * `linkedin_urn` — the URN of the person being returned, can be empty.
</Update>

<Update label="2025-11-18" description="v0.1.0" tags={["People"]}>
  New fields:

  **Person responses**

  * `linkedin_num_id` — can be used to link a person to a URN.
  * `last_updated` — a timestamp of when the person was last updated in the Specter dataset.
</Update>

<Update label="2025-11-15" description="v0.1.0" tags={["Enrichment"]}>
  New endpoints:

  **Reverse email lookup**

  * [Reverse email lookup](/api-reference/enrichment/reverse-email-lookup) — when you have an email address and need to resolve it to a Specter person record so you can standardize contacts, enrich them, or link inbound emails to the correct individual in our database.

  **Text search**

  * [Text search](/api-reference/enrichment/text-search) — turn unstructured text (press releases, bios, notes) into structured entity references you can track, enrich, and join to your downstream systems.
</Update>

<Update label="2025-10-28" description="v0.1.0" tags={["Interest Signals"]}>
  New endpoints added that give the ability to query for investor interest signals.
</Update>

<Update label="2025-09-30" description="v0.1.0" tags={["Companies"]}>
  New endpoint added which gives the ability to [Search company name](/api-reference/companies/search-company-name) and get back basic information for them given a query term.
</Update>

<Update label="2025-08-04" description="v0.1.0" tags={["Companies"]}>
  Two new fields have been added to all endpoints which return companies.

  * `founders_info` — gives more information about the founders including the `specter_person_id` which allows for the person to be looked up either in the App, or via the People API.
  * `specter_strategic_signal_ids` — which indicate strategic signals related to the company.
</Update>

<Update label="2025-06-26" description="v0.1.0" tags={["Companies", "Lists", "Saved Searches"]}>
  * Added a new filter to the [Get company people](/api-reference/companies/get-company-people) endpoint allowing anyone that is a CEO to be returned. This new filter can only be used on its own and founders and department won't be taken into account with this filter.
  * Updated all search and list endpoints to work with a new Share to API toggle. This allows lists and searches to be shared with the API without sharing them with the team.
</Update>

<Update label="2025-06-18" description="v0.1.0" tags={["People"]}>
  A new endpoint for [Get person's email](/api-reference/people/get-persons-email) has been released which allows you to retrieve the professional or personal email address for a person based on their ID.
</Update>

<Update label="2025-06-12" description="v0.1.0" tags={["Enrichment", "People", "Talent Signals"]}>
  * Added endpoints for enrichment of people, which will notify us if there are people we do not have so we can retrieve them.
  * Added endpoints for People and Talent Signals, allowing you to manage and get both using the API.
</Update>

<Update label="2025-05-08" description="v0.1.0" tags={["Companies"]}>
  Added [Get similar companies](/api-reference/companies/get-similar-companies) which returns a list of ids for companies that are similar to the company id being requested. This helps you uncover high-potential companies similar to the one you're referencing and is a powerful way to identify new opportunities, uncover competitors, or expand your investment pipeline with minimal effort.
</Update>

<Update label="2025-02-26" description="v0.1.0" tags={["Companies", "Enrichment", "Lists", "Saved Searches", "Platform"]}>
  First release of the API including:

  * **Enrichment API** — querying to get companies based on parameters (LinkedIn URL, LinkedIn ID, domain, etc.).
  * **Companies API** — get companies by Specter ID or list, and manage lists.
  * **Searches API** — get all available searches and query for companies by search ID.
</Update>
