Guides
Document filters
The vertical-specific filters for patents, news, funding rounds, job openings, research papers, market reports and trends.
Each document category takes its own small set of filters, nested under filters like any other.
- None of them support
geo,TextFilteror the companykeywordsshape. Those arecompany/persononly. - Every date here is a
DateFilter, wrapping its bound underperiod.
patent#
| Filter | Shape | Notes |
|---|---|---|
keywords | KeywordQuery | |
publication_date, application_date | DateFilter | Publication and filing are different events |
status | A bare string | granted, not_granted or all (default). Not a filter object |
application_type | TermsFilter | patent, utility, utility_model, design, plant, provisional, pct, spc |
offices | TermsFilter | USPTO, EPO, JPO, CNIPA, KIPO, UKIPO, DPMA, INPI, CIPO, IPA, INPI-BR, ROSPATENT, IPOS, IPI, WIPO, PCT, EAPO, OAPI, ARIPO, GCCPO |
classification_codes | TermsFilter | CPC/IPC codes with prefix semantics — H01M matches its subgroups. match_all is honoured |
applicants | EntityFilter | The applicant as named on the document |
applied_by_company | EntityFilter | The resolved company the applicant maps to, so a domain matches filings under any of its legal names |
application_ids, publication_ids, family_numbers | TermsFilter | Exact identifiers |
utilityandutility_modelare deliberately distinct: a utility patent is an ordinary patent, a utility model is a much narrower instrument.WIPOandPCTboth resolve to the same authority;ROSPATENTspans two.
{
"category": "patent",
"filters": {
"offices": { "include": ["US"] },
"publication_date": { "period": { "gte": "2024-01-01" } },
"status": "granted"
}
}news_article#
| Filter | Shape | Notes |
|---|---|---|
keywords | KeywordQuery | |
published_date | DateFilter | |
publications | EntityFilter | The outlet — an entity, because outlets need resolving ("TechCrunch" vs techcrunch.com) |
startups | EntityFilter | Companies the article is about |
countries, cities | TermsFilter | The place the article discusses, not the outlet's home. Matched exactly, so casing and spelling must match what is stored |
funding_round#
| Filter | Shape | Notes |
|---|---|---|
funding_size | RangeFilter | Normalised USD; there is no currency field |
stages | TermsFilter | Pre-seed, Seed, Angel, Series A, Series B, Series C, Early stage, Late stage, Growth, Venture, Debt, Grant, Accelerator, Incubator, Crowdfunding, Strategic, Acquisition, Merger, IPO, Post-IPO, ICO |
announced_date | DateFilter | last_updated here is record ingest time, not a data refresh |
companies | EntityFilter | The company that raised |
investors | EntityFilter | Any-of only — "rounds where both A and B participated" is not expressible |
company_country, investor_country | TermsFilter | Distinct: a German company can raise from a US investor |
company_size | RangeFilter | Employee count of the company that raised |
keywords | KeywordQuery | Matches the company's own profile text; this vertical has no round-level free text |
job_opening#
| Filter | Shape | Notes |
|---|---|---|
seniority | TermsFilter | Exactly seven, most senior first: C-Suite, VP, Director / Head, Manager, IC, Entry, In Training. Director and Head are ONE value. Renamed in the 2026-08 taxonomy revamp — a value from an older integration (Senior, Head, C Suite, Intern, President) matches nothing |
department | TermsFilter | One of 23 Function labels: General Management, Sales, Marketing, Revenue Operations, Customer Success & Support, Product, Design / UX, Engineering / Software, Data, Analytics & AI, IT & Infrastructure, Security, Finance, Human Resources / People, Legal, Risk & Compliance, Operations, Supply Chain & Logistics, Medical & Health, Education, Consulting / Professional Services, Research & Development / Science, Real Estate & Facilities, Skilled Trades & Field Services, Unclassified. Only a minority of postings carry one, and an unclassified posting is absent from a filtered result rather than misfiled |
sub_department | TermsFilter | 225 values, populated only where department is |
employment_type | TermsFilter | full_time, part_time, contract, temporary, internship, apprenticeship, seasonal, freelance, volunteer, other. A posting may carry more than one |
work_arrangement | TermsFilter | remote, hybrid, onsite. Any-of only — match_all is ignored, since a posting cannot require every arrangement at once. onsite means neither of the other two is set |
location | TermsFilter | The role's own country/state/city, not the company HQ |
company | EntityFilter | The hiring company, resolved by name/domain/LinkedIn URL |
salary | RangeFilter | Annualised USD even for hourly postings. Only a fifth of postings carry pay, so this filter excludes every posting that omitted it |
posted_date | DateFilter |
This is the one document category where the top-level include_domains /
exclude_domains parameters work, because the posting carries the hiring
company's domain.
Where the old seniority values went (2026-08 revamp)
seniority is a pure career ladder. It used to be a blended taxonomy, corporate
rungs beside occupational classes, but the 2026-08 revamp separated those out:
Educator,Healthcare Professional,Utility WorkerandSpeciality Service Providerare Functions now and belong ondepartment.Founder,Owner,Partner,InvestorandAdvisor(governance) andConsultant/Freelancer(employment type) are not filterable on any axis.
academic_report#
| Filter | Shape | Notes |
|---|---|---|
publication_date | DateFilter | |
paper_type | TermsFilter | article, conference-paper, report, review-article, communication, protocol, … |
publisher | TermsFilter | |
funded_by | TermsFilter | The funding body named on the paper |
citation_count, reference_count | RangeFilter | Citations received, references made |
The narrowest surface of the nine, and there is no keywords field: write the
subject into query instead.
market_report#
| Filter | Shape | Notes |
|---|---|---|
keywords | SingleSetKeywordQuery — not the general shape | Exactly one positive set, and no negative group at all. Two sets or any negative group is a 422, though KeywordQuery accepts both elsewhere |
publisher | TermsFilter | The report's vendor |
industry | TermsFilter | The report's industry classification |
published_date | DateFilter | Roughly half the corpus has no publication date, so filtering on it silently drops those reports |
trend#
| Filter | Shape | Notes |
|---|---|---|
keywords | KeywordQuery | The only filter this category has today |
It matches the trend's own text (name, description, analysis), never its stored keyword definition. "Does this trend discuss X" and "is this trend defined by X" are different questions, and only the first is exposed.