Two search modes, one API — how to pick the right one
Every search and enrich operation comes in two modes that share the same request and response shape — switch between them by swapping database ↔ realtime in the path:
POST /search/database/leads/ POST /search/realtime/leads/POST /enrich/database/company/ POST /enrich/realtime/company/
Decision matrix
Database
Real-time
Data source
Generect’s continuously growing database
Live LinkedIn lookup at request time
Response time
Under 1 second
5–60 seconds
Price
Lower
Higher
Lead freshness
Updated within the last 12 months
As of the moment of the request
Filters
Core set (see below)
Full set — keywords, past companies, schools, groups, live signals
Count endpoints
Free, instant
Billable, per request
Nothing found
0 results, $0 — no hidden live fallback
No Data — No Charge
Start with database mode: it answers instantly and costs less. Switch the same request to realtime when you need data fresh as of today or filters database mode doesn’t support.
When to use which
Use database when:
you process volume and care about cost and speed (list building, scoring, backfills)
last-year freshness is acceptable for your workflow
you want free counts to size an audience before paying for results
Use real-time when:
the record must be current right now (job changes, new role verification)
you need advanced targeting: keywords, past_company_names, schools, groups, functions
you need live signals (changed_jobs: changed jobs in the last 90 days, posted_on_linkedin: posted in the last 30 days), personas, or search_emails
Filters supported in database mode
Leads:job_titles, seniorities, locations, exclude_locations, company_locations, exclude_company_locations, company_industries, exclude_company_industries, company_headcounts, exclude_company_headcounts, company_types, gender, seniority_levels and exact_locations (database mode only) — plus targeting a single company via company_id, company_link, or company_name.Companies:industries, exclude_industries, headcounts, locations, exclude_locations, company_types. The sub_industries toggle is also accepted here and behaves the same as in real-time mode (it modifies industries rather than counting as a filter on its own).Anything outside this set is rejected with 400 and a message pointing to the realtime endpoint, so an unsupported filter is never silently ignored. At least one search filter is always required.
A supported filter given an unknown value is a different matter, and the
behaviour is not uniform:
locations, exact_locations, company_headcounts, company_types, gender and
seniority_levels reject an unknown value with 400, naming the field (the
headcount, gender and seniority level errors also list the valid values).
company_industries / industries and seniorities do not validate.
An unrecognised value simply matches nothing, so the request succeeds, returns
0 results and charges \$0.
So company_industries: ["Fintech"] — not a LinkedIn industry — looks exactly
like a real empty audience. Industry and seniority values are matched
exactly: use the names from
ICP Search, and when a count comes back as zero, re-check
the spelling before concluding the audience does not exist.
Billing
Both modes charge per returned result at their own rate — real-time costs more than database. If nothing is found, nothing is charged. Database lead and company search can also return thin rows for free with "detail": "thin", up to a daily quota per account: see Search database leads. Exact prices for your account are in your billing settings.