Skip to main content
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.
CompaniesPeopleInvestorsSignalsTransactionsListsSaved Searches
v0.1.0
This is a big release. We’ve reorganised the API around a cleaner, more consistent set of endpoints, retired sixteen of the older ones, added ten new endpoints, and changed a number of prices and field names. Everything you need to act on is below.Sixteen endpoints are retiredFifteen have a drop-in replacement. The sixteenth, Text search, doesn’t: Search entities by name will resolve a name for you, but nothing replaces pulling entities out of free text. Repoint your calls and you’re done; the retired paths now return 404.Ten new endpointsTen new endpoints have been added:Saved searches can be created, and cover the transaction productsCreate saved search saves an existing query under a name. Pass the query_id that AI search returns, plus a name. The search is assigned to an admin of your organisation and reports them as owner_id; only an admin-owned search can be deleted through the API. The product comes from the saved query rather than the request, and the search is shared with the API and your organisation on creation, so it is readable straight away. Free.Until now a saved search could only be created in the app and shared from there, and the API could delete a search it had no way of making.Saved searches for the three transaction products are now readable too, matching the five that already were:Each results item is the same object the matching by-date feed returns, so it parses identically. Detail endpoints are free; results cost 1 credit per result returned.Company funding rounds name their companyGet company funding rounds returns company_id and company_name on every row, matching Get investor funding rounds and Get funding rounds by date. A row stays attributable once it is separated from the request that produced it. investor_count stays specific to the company-scoped endpoint.Get funding rounds by date schema correctedThe reference documented Get funding rounds by date with the company-scoped round shape, which carries investor_count. The endpoint returns the cross-company shape, which does not. The response itself has not changed, only its documentation.PricingThe following prices have changed:One page size, 50, on the paginated readsThese endpoints charge one credit per request for a page of up to 50 results, and the page limit now matches that unit everywhere: previously up to 1000 (Get company funding rounds, Get company acquisitions, Get company IPOs, Get company news, Get investor funding rounds, Get network people, Get network companies); previously up to 100 (Get company employees); previously up to 25, so these now return more per page (Get acquisitions by date, Get funding rounds by date, Get IPOs by date); newly paginated (Get network connections at a company pages its contacts, while roles and connected_teammates still describe the whole company).Sending limit above 50 now returns 422 rather than a larger page. The default is unchanged at 50, so a caller that never set limit is unaffected; one that set it higher should drop to 50 and page with page.AI search costs one credit per 5 resultsAI search is billed per 5 results returned, rounded up, instead of 1 credit per result. A full page of 50 costs 10 credits where those 50 results used to cost 50, three results cost 1, and a query that matches nothing costs nothing. Results are cached at the organisation level for 7 days, so an identical query from your team within that window returns the cached result. Pagination now works like the other paginated reads: 50 results a page, up from 25, walked with page and limit, with X-Total-Count, X-Page, X-Page-Size, X-Total-Pages and Link describing the position. limit above 50 returns a 422, and paging a query returns the same result set throughout, so a record does not move between pages as you walk them.Poll a saved search from a moment you choose: new_results_afterEvery saved-search results endpoint accepts new_results_after, a timestamp such as 2026-07-10T00:00:00Z. Results are then limited to the records added to that search on or after it, so a scheduled job passes back the timestamp of its last read and receives exactly what arrived in between, with no double-reads and no gap. All eight products support it: companies, people, investors, talent signals, investor-interest signals, funding rounds, acquisitions and IPOs. Additions are tracked for 60 days. A cutoff older than that returns 422 with NEW_RESULTS_AFTER_BEYOND_RETENTION, rather than an answer that silently omits pruned rows.This deprecates new. The new flag restricted results to a fixed this-week window; new_results_after does the same job with a window you control, and takes precedence when both are sent. new is no longer documented anywhere in this reference: on the saved-search results endpoints, on Get revenue signals by date, Get company revenue signals or Get investor-interest signals by date. Existing calls that send it keep working for now, but move them over: use new_results_after on a saved search, or the endpoint’s *_date_after bound for a publication-date window.Request changesEnrich company accepts a new pitchbook_url identifier alongside domain, website_url, linkedin_url, linkedin_id and crunchbase_url. Find company ID accepts crunchbase_url (an organisation profile) and pitchbook_url; both behave like linkedin_url, with exactly one identifier per entry, at most one match, and match_confidence 1, and both accept http/https, www, query strings and anchors. Still free.Get company acquisitions gains acquired_date_after / acquired_date_before, and Get company funding rounds gains funding_announced_date_after / funding_announced_date_before. Both bounds are inclusive.Get company competitors no longer accepts refresh. Freshness is decided internally: results older than 30 days are recomputed automatically. Sending refresh now returns 422.growth_stage values now match the filter vocabularyThe company object’s growth_stage was serialised with its own display labels, while the growth_stage filter parameters accepted the underlying values, so the same field spoke two vocabularies depending on whether you were reading or filtering. The response now returns the same values the filters take:Two consequences worth noting: bootstrapped previously absorbed companies with no funding at all, which now report no_funding distinctly; and pre_launch was already being returned despite never appearing in the documented enum. If you match on growth_stage strings, map them using the table above. If you pass the value straight into a growth_stage filter, that now works without translation.Growth and funding highlights removedThe deprecated highlight filters and their counts are gone from every endpoint that carried them. Removed query parameters: newGrowthHighlights and newFundingHighlights on Get company saved search results and Get company list results. Removed response fields: new_growth_highlights_count and new_funding_highlights_count on Get company saved search and Get all saved searches. new_count still reports companies first seen in a search.The bulk lookups are grouped with the enrichment endpointsThree bulk endpoints have moved into the Enrich group and been renamed to match what they do. Each accepts the same identifiers as its single-record enrich counterpart (a domain, website, LinkedIn URL and so on) and returns the same enriched records, just up to 50 per request, so they now sit alongside those endpoints under names that describe them.Paths, request bodies, responses and prices are unchanged, so there’s nothing to do in your integration beyond updating your bookmarks.Enrichment context field renamedEnrich person returned its enrichment context timestamp as updatedAt, the one camelCase field on the API where every other field is snake_case. It is now updated_at. The value and format are unchanged.People list entries are keyed person_idGet people list names each entry’s identifier in people[] as person_id, matching the company_id and investor_id its sibling endpoints already use. The old people_id key is gone.raised_amount_usd is a number on investor fundsEach entry in an investor’s fund_details[] returns raised_amount_usd as a JSON number rather than a string: 750000000, not "750000000". This affects every endpoint that returns an investor: Get investor by ID, Enrich investors (bulk), Enrich investor, Get investor list results and Get investor saved search results. The funding round endpoints already returned a number here.hq.region is now hq.continentThe hq.region deprecation announced on 2026-03-20 is enforced: the field is gone. hq.continent carries the same value from the same source, so the fix for a caller still reading region is a one-line rename. It applies everywhere an hq is returned: Get company by ID, Find company ID, Search entities by name, and the company.hq and person.location blocks on the investor-interest signal endpoints. hq.regions, the plural metro-area groupings such as ["San Francisco Bay Area", "United States"], is unchanged and stays specific to Get company by ID. It is a different field from the company’s top-level regions, which carries a single country-level grouping.Company employees carry the full person recordGet company employees returns each person’s own profile alongside their role at the company: first_name, last_name, profile_picture_url, linkedin_url, linkedin_num_id, twitter_url, github_url, tagline, location, region, highlights, talent_signal_ids and investor_signal_ids. A team page that took one Get person by ID call per employee is now a single request. Follow person_id for the fields that stay profile-only: experience, education, skills and languages. The region here is the person’s own region, independent of the company’s hq.The by-email endpoints return the full person recordEnrich person by email and Enrich people by email (bulk) return the same person object as Get person by ID, plus the email each result resolved from and the match score. Every profile field is now included, so a match no longer needs a follow-up call. The seven-field summary these endpoints used to return is gone, and company_id is no longer a top-level key; a person’s roles live in experience[], each with its own company_id. Pricing is unchanged at 2 credits per matched result, and an unmatched address still returns 204 on the single endpoint and is still omitted from the bulk response.is_global and shared_with on listsThe list endpoints return two new fields, on both the collection and the per-list response: is_global, which is true for lists curated by Specter, and shared_with, the Specter user IDs the list is shared with, or [] when it is not shared. Resolve an ID to a person with Get organization members. This applies to Get all company lists, Get company list, Get all people lists, Get people list, Get all investor lists and Get investor list. Get all saved searches also carries is_global, which the per-product saved-search endpoints already returned.Smaller changeswebsite.domain_aliases returns [] rather than null when a company has no alias domains, matching organization_name_aliases.What you need to do: move off the sixteen retired paths using the table above, drop refresh from any competitors request, stop sending newGrowthHighlights / newFundingHighlights and stop reading the two *_highlights_count fields, read context.updated_at instead of context.updatedAt on enrich-person, drop any limit above 50 on AI search and on the per-entity paginated reads and page for more, stop sending new and use new_results_after or the endpoint’s date bounds instead, read person_id instead of people_id on people list entries, parse fund_details[].raised_amount_usd as a number, read experience[] instead of the top-level company_id on the by-email endpoints, rename hq.region to hq.continent, and re-check your credit budgeting against the new prices, including the doubled email lookups.
Platform
v0.1.0
Plan change:One API planThe Enrichment-only plan is retired. Every approved key now reaches the whole endpoint surface — the enrichment endpoints (Enrich company, Enrich person, Enrich investor) alongside the databases, signals, saved searches, lists, and network endpoints.No migration is needed. No key was provisioned on the Enrichment-only plan, so every call that worked before behaves identically. See Plans & Pricing.
AccountSearch
v0.1.0
New endpoints:Get credit balance: GET /organization/creditsRead your organization’s credit position for the current billing window without contacting support: credit_limit, used, remaining, and unlimited. A credit_limit of -1 means unlimited. The endpoint is free, and it stays readable when your balance is exhausted, so you can always check where you stand, even after a 402.Search entities by name: GET /entities/searchOne name search across companies, people, and investors, returning basic records grouped by entity type. Pass types to narrow the search and limit (1–50) to cap matches per type. Also free.This replaces the three per-entity name searches, which are being retired: GET /companies/search, GET /people/search, and GET /investors/search. Migrate to GET /entities/search: it covers all three in one call and costs nothing.
CompaniesPeopleInvestors
v0.1.0
Breaking change:Deprecated industry taxonomy removedThe legacy industries and sub_industries fields are no longer returned by any endpoint. They were superseded by industry (the Specter v2 taxonomy) and tech_verticals, both of which have been returned alongside them for some time.What you need to do: read industry instead of industries, and tech_verticals instead of sub_industries. If you mapped the legacy values yourself, note that the v2 taxonomy is not a one-to-one renaming, so review the values you depend on.is_global on company saved searchesGet company saved search now returns is_global, matching the investor, people, talent and investor-interest saved-search endpoints and the generic Get all saved searches. It is true for global searches curated by Specter and false for searches owned by your organization.
Companies
v0.1.0
Breaking change:Company responseThe ipo[] block on the company object is now serialised in snake_case, keyed exactly like the IPO endpoints (Get company IPOs, Get IPO by ID). The camelCase keys are no longer returned.The values are unchanged: these amounts were already in USD, and the _usd suffix now says so. This was the last camelCase block in the API; every response field is snake_case from here.What you need to do: update any integration that reads a key from company.ipo[] to the new name in the table above.
Companies
v0.1.0
Correction:Enrich companies (bulk)POST /companies/by-id/bulk returns a bare JSON array of company objects, the same schema as Enrich company. Identifiers that don’t match a known company are silently omitted from the response. This corrects the 2026-06-09 entry below, which described each row as a { status, company, enrichment } wrapper; no such wrapper exists. Update any integration that reads a per-row status field.
Account
v0.1.0
New endpoints:

Account

GET /health: returns 200 {"status":"OK"} while the API is up and able to reach its backing databases. Unauthenticated and free.
Account
v0.1.0
GET /logs entries now include two new fields: credits_consumed (the number of credits the call drew from your plan, or null if not known; older rows aren’t backfilled) and request_id (a UUID matching the X-Request-ID response header, useful when contacting support about a specific call).
Search
v0.1.0
Breaking change:AI searchThe AI search resource_type parameter has been renamed to product, in both the request body and the response. The enum values are unchanged. Update any integration that sends or reads resource_type to use product.
SignalsInvestors
v0.1.0
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:
Search
v0.1.0
New endpoints:AI searchAI search turns a natural-language query into a structured search across all products and returns matching records. Set product 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.
CompaniesSignals
v0.1.0
New endpoints:Companies
  • Find 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 — 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 company revenue signals — 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.
Companies
v0.1.0
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.
Companies
v0.1.0
New endpoints:Companies
  • Get company latest revenue — 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 company latest valuation — 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.
Signals
v0.1.0
New endpoints: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.
  • Get revenue signals by date — list revenue (and profitability) signals, newest first. Each item is the same signal object returned by Get Revenue Signal by ID.
  • 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 — 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.
Platform
v0.1.0
Credit-limit responses now return 402Running 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.
EnrichCompaniesInvestorsSignals
v0.1.0
Bulk EndpointsNew 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
  • Enrich companies (bulk) — bulk counterpart to Enrich company; 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.
  • Enrich people (bulk) — bulk counterpart to Enrich person; 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.
  • Enrich people by email (bulk) — bulk counterpart to Enrich person by email; reverse-lookup people from email addresses.
Companies
  • Get similar companies (bulk) — bulk counterpart to Get similar companies; find lookalike companies for multiple seed company IDs at once.
InvestorsTalent and Interest Signals
  • Bulk get Talent Signals by ID — bulk counterpart to Get Talent Signal; fetch talent signals by ID. Duplicate IDs are honored.
  • Bulk get Investor Interest Signals by ID — bulk counterpart to Get Investor Interest Signal by ID; fetch investor interest signals by ID. Duplicate IDs are honored.
CompaniesPeopleInvestors
v0.1.0
Name based search for companies, people and investorsName-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 — 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 person.
Investor search
  • 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. Enrich investor (lookup by website / exact name) is unchanged.
Company search
  • 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_confidenceAll 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.
Network
v0.1.0
New endpoints:Network MappingThree 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 network people — 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 network companies — 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 network connections 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
  • Get organization 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.
Signals
v0.1.0
New endpoints: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 company news — 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.
Enrich
v0.1.0
New endpoints:Investor lookup
  • Enrich investor — 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.
InvestorsListsSaved SearchesTransactions
v0.1.0
New endpoints: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 — 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 — 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 — returns all investor lists created with the API, shared with the API, or shared globally, including the count of investors in each list.
  • Create investor list — create a new investor list.
  • Get investor list — retrieve details of a specific investor list, including the investor IDs it contains.
  • Update investor list — modify an existing investor list.
  • Delete investor list — delete an investor list.
  • 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.
TransactionsThree 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:Acquisitions:IPOs:
  • Get IPO by ID — a single IPO with the issuing company, exchange and ticker symbol, listing date, and proceeds in USD.
  • Get company IPOs — IPOs by company.
Platform
v0.1.0
New endpoints:API Call Logs
  • Get 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)
Signals
v0.1.0
New parameters:Talent search results & Investor Interest search resultsBoth 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:
CompaniesSignals
v0.1.0
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.
PeopleEnrich
v0.1.0
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.
People
v0.1.0
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.
EnrichCompanies
v0.1.0
New endpoints:Enrich person by email
  • Enrich person by email — 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.
Resolve entity from text
  • POST /entities/text-search — turn unstructured text (press releases, bios, notes) into structured entity references you can track, enrich, and join to your downstream systems.
Signals
v0.1.0
New endpoints added that give the ability to query for investor interest signals.
Companies
v0.1.0
New endpoint added which gives the ability to Search company name and get back basic information for them given a query term.
Companies
v0.1.0
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.
CompaniesListsSaved Searches
v0.1.0
  • Added a new filter to the Get company employees 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.
People
v0.1.0
A new endpoint for Get person email has been released which allows you to retrieve the professional or personal email address for a person based on their ID.
EnrichPeopleSignals
v0.1.0
  • 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.
Companies
v0.1.0
Added 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.
CompaniesEnrichListsSaved SearchesPlatform
v0.1.0
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.