Data catalog / search

Search data

Search for people, companies, employees, jobs and web results. People search filters on job title, industry, location, company domain and headcount at 0.1 credits per result. This page maps each search question to the endpoint that answers it.

In short: RichAPI's search endpoints: POST /people_search (job_title, industry, location, domain, linkedin, employee_size_start and employee_size_end, zero-based page, limit; 0.1 credits per result), POST /profile_search (name, title, company, school, location; 0.1 per result), POST /linkedin_company_search (0.1 per result), POST /linkedin_company_employees_search (company LinkedIn URL; 0.1 per result), POST /linkedin_job_search (0.1 per result), POST /google_search_scraper_sync (1 credit per result), POST /search_bing (1 credit per call), POST /search_google_trends (1 credit per call), POST /geo_id_search (0.01 credits) and POST /search_reference_data (free). Per-result searches bill only for rows returned.

Last updated October 13, 2026

Pick the search by the question

Question Endpoint
Who holds this title, in this industry, in companies this size? people_search
Who is this person? (name, company, school) profile_search
Who works at this company? linkedin_company_employees_search
Which companies match a name, size, industry and location? linkedin_company_search
Who is hiring for this role? linkedin_job_search
What does Google or Bing return for this query? google_search_scraper_sync, search_bing
Is interest in this topic rising? search_google_trends

For seniority, function, tenure, job changes and exclusion filters, use lead search instead.

People search

POST /people_search combines filters on the company (domain, industry, employee_size_start and employee_size_end, linkedin company URLs) with filters on the person (job_title, location). Each filter takes a list, so ["Founder", "CEO"] matches either title. page counts from 0, and limit sets the page size.

The response says how many matches exist in total (totalElements) and how many pages that makes (totalPages), so one small first call tells you how big the list is before you pull it. How to build a prospect list from title, industry and location has the full walkthrough.

Endpoints and rates

Endpoint What it does Credits Billed
/people_search Search LinkedIn profiles by company/account and contact filters such as domain, industry, employee size, job title, and location. 0.1 per result
/profile_search Search LinkedIn profiles by name, title, company, location and more. 0.1 per result
/linkedin_company_search Search LinkedIn companies by name, location, size, and industry. 0.1 per result
/linkedin_company_employees_search Search for employees of a specific company using its LinkedIn URL. 0.1 per result
/linkedin_job_search Search LinkedIn jobs by title, company, location, and more. 0.1 per result
/google_search_scraper_sync Scrape Google Search results synchronously. 1 per result
/search_bing Search Bing and get structured SERP results with titles, URLs, and descriptions. 1 per call
/search_google_trends Get Google Trends data: interest over time, related queries, and rising queries for any keyword. 1 per call
/geo_id_search Resolve a location name to a LinkedIn Geo ID for use with profile and lead search filters. 0.01 per call
/search_reference_data Returns all valid filter labels (seniority levels, industries, functions, etc.) for use with Lead Search. 0 free

Rates are read from the live OpenAPI spec. Credits are prepaid and never expire, and the price of a credit depends on your package: see pricing.

What search costs

Most searches bill per result returned, with no charge for the call itself. 0.1 credits per result means 1,000 people cost 100 credits, and a search that matches nobody costs nothing.

The web searches price differently. Google search bills 1 credit per result returned. Bing and Google Trends are 1 credit per call. geo_id_search costs 0.01 credits and search_reference_data is free.

Search is usually the cheapest step in a list-building job. Finding and verifying emails for the rows you keep costs more, so filter hard before that step. People search to email waterfall breaks down the cost of each leg.

Search in a list-building job

Reference

limitinteger · Required
Number of items per page.
pageinteger · Required
Page number, zero-based.
domainarray of object · Optional
Company domains.
employee_size_endinteger · Optional
Maximum employee count.
employee_size_startinteger · Optional
Minimum employee count.
industryarray of object · Optional
Industry names.
job_titlearray of object · Optional
Job titles to match.
linkedinarray of object · Optional
LinkedIn account URLs.
locationarray of object · Optional
Locations to match.

Request

Minimum required parameters for a search data call.

Request
{
  "job_title": [
    "Founder",
    "CEO"
  ],
  "industry": [
    "Software Development"
  ],
  "location": [
    "United States"
  ],
  "employee_size_start": 11,
  "employee_size_end": 50,
  "page": 0,
  "limit": 25
}

See it in a workflow

Playbooks

Real patterns, recipes, and prompts other builders run on RichAPI

Start free with 100 credits

Developer Docs

Auth, request shape, and error handling

See Documentation

FAQ

Frequently asked questions

Search for people, companies, employees, jobs and web results. People search filters on job title, industry, location, company domain and headcount at 0.1 credits per result. This page maps each search question to the endpoint that answers it.
Every endpoint is billed from the same credit pool, at the published rate on /pricing — never a separate contract per endpoint.
Yes — the same endpoint is reachable from an MCP client (Claude, ChatGPT, Cursor, Windsurf) using the same key and credit pool. See /mcp.

Related data