Endpoints
Company records
Fetch full company records by internal id, or resolve raw domains, LinkedIn URLs and names.
/v1/entities/companiesLook up companies by id
Scope: dsp.entities.read
Use it when you already know which companies you want (by internal id,
domain, LinkedIn URL, or name) and need their full records. Outcome: one
result per id you sent, in order. Found records sit under matches; misses are
reported as found: false with an empty list rather than dropped. Worked use
cases: Record Lookup guide.
Two ways to call it, distinguished by by:
by | ids are |
|---|---|
| omitted | The platform's own internal (prism) ids |
domain | Company domains |
li_url | LinkedIn URLs |
name | Company names |
auto | Classified entry by entry (the same detection /v1/similar applies to anchors) |
The id on a search or similar hit is not an internal id: it is the company's
domain or an opaque hash, so it does not resolve with by omitted. Look a hit up
by its own fields instead: a company with by: "domain" and its domain, a
person (on /v1/entities/persons) with
by: "li_url" and its linkedin_url. For documents, see
Document records.
Request#
by"auto" | "domain" | "li_url" | "name" | nullWhen set, ids are raw identifier values instead of prism's internal id: auto classifies each one independently (mirrors the anchor detection /v1/similar uses); any other value forces every entry to that one kind. Omit for the default: ids are prism ids. The id on a search or similar hit is not a prism id (it is the company's domain or an opaque 16-hex hash), so look a hit up by its own fields instead: a company with by: domain and its domain, a person with by: li_url and its linkedin_url.
fieldsarray of string | nullRestrict the returned fields. Omit for the full record.
idsarray of string, ≥ 1, ≤ 1000requiredHeaders
Idempotency-KeystringMakes a retry safe. Send a unique value per request and reuse it when you retry that same request: with the same body and credential, on the same UTC day, rows already charged are not charged again.
Idempotency-Key is optional. Send it when you might retry: the same key, on
the same request, from the same credential, on the same UTC day is not charged
again for records already paid for. See
Retries.
Response#
Each results[] row is an EntityHit: the echoed input (id), whether it
resolved (found), and the company records under matches — restricted to
your fields projection when you sent one, the full record otherwise.
matches is always a list, and for companies it holds at most one record:
- A company id or domain is unique by construction, so an id or
by: "domain"lookup returns exactly one match and a miss returns none. by: "name"returns the best-ranked match for each name. A name is not a unique key, so check the record you get back (itsdomain, for instance) before you rely on it.
The list shape is shared with the document routes, where a name lookup can return several records, so a caller never branches on which route it called.
attributionarray of Attributionas_ofstring | nulldomainstring | nullquotestring | nullRESERVED for per-fact citation. Always null in v1.
source_corpusSourceCorpusWhere content came from. Closed set — it appears in attribution[]. The first four are the GTM entity graph. The rest are the document corpora behind the non-entity categories, each a distinct index with its own refresh cadence — which is the reason they are named separately rather than lumped under one label: attribution[].as_of means nothing if two corpora updated a month apart share a name.
urlstring | nullRESERVED for per-fact citation. Always null in v1.
columnsarray of object | nullThe answer table's columns, in order, when a run carries extra columns beyond the entity's own fields -- a job-opening link, a value joined from another dataset. Each entry is {name, description, source}; the value for each sits on every row in results keyed by the column name. Null means a plain entity table. Additive, so it breaks no existing client.
coverageCoverage | nullHow much of the addressable set this answer represents. Null means coverage was not measured for this request -- fast and auto do not enumerate -- and never that coverage was zero. Additive, so it breaks no existing client.
auditedbooleandefault: falseWhether the query was checked against the executed filter for dropped requirements. Reported because an empty constraints_unmet only means something if something looked.
constraints_unmetarray of stringRequirements in your query that the search could not express, in your own words. Non-empty means part of the question was not answered -- most often because it needs a dataset this search cannot reach (job postings, employment history, patents, news, funding dates). When this is non-empty, universe_exhausted is withheld: 'we returned everything that matches' cannot be true of a question that was never asked.
criteriaarray of objectPer criterion: evaluated, passed, success_rate, and whether it was *proven* by the query or *judged* by a model. Without this a thin result leaves the caller guessing which requirement thinned it.
enumeratedintegerHow many of them this answer carries. ≥ 0.
enumeration_recallnumber | nullenumerated / universe. Null when the universe was not exact, because a ratio over an estimate is not a recall figure. Note this measures coverage of the *resolved query*, not of the user's intent -- a wrong predicate can be exhaustively enumerated. ≥ 0, ≤ 1.
linkagearray of objectOne entry per other dataset this answer joined against: corpus, join_key, observable, of_constrained, ratio, is_lower_bound. ratio is the fraction of your matching accounts that dataset can even see -- measured at 5-60% depending on the dataset and how large the companies are, and never 100%. Non-empty therefore means universe_exhausted is withheld by construction: we returned everything reachable, and a dataset cannot see the rest.
linkage_coveragenumber | nullThe joins combined, as a product rather than a minimum: two datasets seeing 27% and 24% of your accounts jointly see about 6.5%, not 24%. Null when no join was performed or when any leg's coverage is unknown.
linkage_coverage_is_lower_boundbooleandefault: falseTrue when a key set was capped or coverage was estimated rather than measured, making linkage_coverage a floor. Narrowing the question makes it exact.
similarityarray of objectNarrowings done by ranking rather than by predicate. Each entry carries the concept, how many ids it resolved to, the k asked for, whether the list was cut at that ceiling, and the fraction of candidates that could be compared at all. Non-empty means universe_exhausted is withheld on purpose: a cosine is a degree, so a top-k ranking has no complete state, and 2.9% of companies carry no embedding to compare.
truncated_bystring | nullWhich limit stopped the enumeration short, when one did.
universeintegerRecords matching the resolved query, counted, not sampled. ≥ 0.
universe_exhaustedbooleandefault: falseEvery matching record was returned and the count agrees. The claim an unbounded-corpus search engine cannot make.
universe_is_exactbooleanFalse when the count hit a cap. Always serialized: a capped count presented as exact is the same lie as an unmeasured one.
degradationarray of Degradationdetailstringimpact"recall" | "precision" | "freshness" | "fields"reasonDegradationReasonWhy an answer is less than it should be. Closed, because a client that cannot branch on the reason can only show the user a shrug. These are the honest constraints — partial vector coverage, smry mapped as keyword so it cannot be scored lexically, a federated corpus being unreachable — surfaced at runtime instead of in a footnote.
source_corpusSourceCorpus | nullhas_morebooleanmetaResponseMetaPresent on every 2xx, including the ones that are not paginated.
as_ofstringcredential"api_key" | "session"default: api_keyWhich credential produced this response. session means the dashboard playground ran it as the signed-in user rather than as an API key — so it is billed to the user, subject to interactive rate limits, and carries no integration compatibility guarantee. Additive and defaulted, so it breaks no existing client.
credits_chargednumber | nullWhat this request cost, in credits, to at most three decimals. 0 when it cost nothing: a Basic or AI search that found nothing, rows this search already paid for (a cursor sent again, or a request repeated with the same Idempotency-Key on the same UTC day), or a test key. A request without a cursor or a repeated key is a new search, so keep the first page rather than asking for it again. null on a free endpoint.
environment"live" | "test"Echoed on every response so a developer can never mistake a test-key result for a live one.
request_idstringnext_cursorstring | nullOpaque and signed. Invariant: has_more == (next_cursor is not None). There is no page or offset parameter — not accepted, not deprecated, never present.
resolved_searchResolvedSearch | nullcategoryEntityCategory*What* to search, and what a returned row is. One parameter carries both, because they are the same fact: a search of patent returns patents. The alternative — a source/vertical selector beside a narrower category — lets a caller ask for patents from the people index, a combination that has no meaning and would need rejecting at runtime. A closed set that cannot express the contradiction is better than a validator that catches it. Values are exactly prism's own row types, so category in the request and results[].category in the response are always the same string. company and person are the GTM index; the rest are separate corpora with their own filters, freshness and coverage. Not everything applies everywhere: see SearchRequest, which rejects the GTM-only parameters rather than ignoring them. job_opening is a document corpus like patent/news_article/etc — a posting, not an entity — but its records carry a domain (the posting company's) all the same. It is deliberately not in GTM_CATEGORIES (that set is about the entity/document distinction, and a job posting is still a document), but it *is* in DOMAIN_FILTERABLE_CATEGORIES, which exists specifically to separate those two axes.
conflictsarray of objectfiltersFiltersfilters_source"caller" | "parser" | "caller+parser" | "none"default: nonemode"fast" | "auto" | "deep"How hard to work on the query. The distinction is *what the words mean*, not how many results come back: - fast — match my words. The query is matched by meaning (vector retrieval, falling back to keywords where vectors are unavailable); no LLM in the path, so nothing is extracted into filters. - auto — understand my intent. The parser extracts filters. - deep — reason about it. Multi-step, slowest, most expensive. fast was very nearly defined as "filters only, no LLM", which would have made query — the primary parameter — silently inert. A parameter that does nothing is worse than one that is missing.
overridesarray of objectparser_versionstringquerystring | nullsemantic_querystring | nullsemantic_scope"company" | "person" | nullsortarray of objectresultsarray of EntityHit[CompanyRecord]categoryEntityCategory*What* to search, and what a returned row is. One parameter carries both, because they are the same fact: a search of patent returns patents. The alternative — a source/vertical selector beside a narrower category — lets a caller ask for patents from the people index, a combination that has no meaning and would need rejecting at runtime. A closed set that cannot express the contradiction is better than a validator that catches it. Values are exactly prism's own row types, so category in the request and results[].category in the response are always the same string. company and person are the GTM index; the rest are separate corpora with their own filters, freshness and coverage. Not everything applies everywhere: see SearchRequest, which rejects the GTM-only parameters rather than ignoring them. job_opening is a document corpus like patent/news_article/etc — a posting, not an entity — but its records carry a domain (the posting company's) all the same. It is deliberately not in GTM_CATEGORIES (that set is about the entity/document distinction, and a job posting is still a document), but it *is* in DOMAIN_FILTERABLE_CATEGORIES, which exists specifically to separate those two axes.
foundbooleanidstringmatchesarray of CompanyRecordaccount_namestring | nullacquired_byarray of Dealamount_usdnumber | nullannounced_onstring | nullcompanystring | nullacquisitionsarray of Dealamount_usdnumber | nullannounced_onstring | nullcompanystring | nullbusiness_classificationstring | nullbusiness_modelsarray of stringcitystring | nullclientsarray of stringcompany_keywordarray of stringcompany_typesarray of stringcountrystring | nulldepartment_headcountobject | nulldescriptionstring | nulldomainstring | nullemployee_countinteger | nullemployee_rangeEmployeeRange | nullmaxinteger | nullmininteger | nullemployees_by_countryobject | nullfacebook_urlstring | nullfounded_yearinteger | nullfunding_roundsarray of FundingRoundamount_usdnumber | nullannounced_onstring | nullinvestorsarray of stringtypestring | nullfunding_stagestring | nullglobal_presenceGlobalPresence | nullcountriesarray of stringcountry_countintegerdefault: 0hq_countrystring | nullgovt_non_govtstring | nullgrowth_stagestring | nullidstring | nullindustrystring | nullinvestorsarray of stringipo_statusstring | nulljob_openingsstring | integer | nulllast_funding_amountnumber | nulllast_funding_datestring | nulllatitudenumber | nulllegal_namestring | nulllinkedin_followersinteger | nulllinkedin_urlstring | nulllocationstring | nulllogostring | nulllongitudenumber | nullnaicsarray of stringoffice_locationsarray of OfficeLocationaddressstring | nullcitystring | nullcountrystring | nulloperating_statusstring | nullother_industriesarray of stringownershipstring | nullparent_organizationOrganisation | nullnamestring | nulltypestring | nullpartnershipsarray of stringpostal_codestring | nullproductsarray of Productdescriptionstring | nullnamestring | nullprofit_non_profitstring | nullregionarray of stringrevenuenumber | nullrevenue_rangeRevenueRange | nullmaxnumber | nullminnumber | nullshort_descriptionstring | nullsicarray of stringstatestring | nullstreet_addressstring | nullsub_industrystring | nullsubsidiariesarray of Organisationnamestring | nulltypestring | nullsuppliersarray of stringtechnologyarray of stringtotal_fundingnumber | nulltwitter_urlstring | nullwebsitestring | nullsuggestionSearchSuggestion | nullA better way to have asked this question -- a different category (kind: search), or agentic search via POST /v1/agents (kind: agentic). Advisory: these results came from the search that was asked for, whatever this says. Null when there is nothing worth suggesting, which is the common case. Additive, so it breaks no existing client.
categoryEntityCategory | nullThe category to search instead. Set iff kind is search.
kind"search" | "agentic"search — a different category fits. agentic — no single search fits; use POST /v1/agents.
messagestringOne ready-to-show sentence.
totalinteger≥ 0.
total_is_estimatebooleanAlways serialized, never defaulted away. A field clients can forget exists is a field that renders an estimate as exact.
Errors#
| Status | Code | Summary |
|---|---|---|
| 401 | auth.unauthorized | No usable credential (cause deliberately unspecified) |
| 402 | credits.insufficient | The allocation cannot fund this action |
| 403 | auth.browser_origin | A secret key was used from a browser |
| 403 | auth.insufficient_scope | The credential does not hold the required scope |
| 422 | pagination.cursor_invalid | The cursor could not be read (e.g. a filter changed mid-pagination) |
| 422 | request.invalid | A field failed validation (extra.errors has the detail) |
| 429 | quota.burst_exceeded | Interactive burst limit hit — wait Retry-After seconds |
| 503 | credits.unavailable | The billing service could not confirm the charge; retry with the same Idempotency-Key |
| 503 | upstream.unavailable | The retrieval engine is unreachable (not charged) |
| 504 | upstream.timeout | The retrieval engine did not answer in time (not charged) |