Skip to content

HireLayer Talent Pool Search · Talent Pool Search API

Talent Pool Search API that finds the resumes closest to a job

Send a job, stored or as text. HireLayer Talent Pool Search looks through the resumes already in your workspace and returns their application_ids, closest first, each with a similarity. Filter by city and radius or by date added, then send the ones you choose to Resume Scorer for the evidence.

Schedule a demo
Endpoint
POST /api/v4/resumes/search
Input
job_id or job text · filters
Response
application_id · similarity
Billing
1 credit per search
HireLayer Talent Pool Search, POST /api/v4/resumes/search. A stored job, filtered on Paris within 30 km and resumes added after January 2026, returns the closest resume of the database, with a similarity of 0.57. Values come from the documented API example.

What the Talent Pool Search API finds

Problems it solves

  • Past applicants are forgotten

    Resumes received for earlier jobs sit in the database while recruiters source from scratch for the next one.

  • Keyword search misses close profiles

    A boolean query on job titles leaves out people who did the same work under another title.

  • Scoring the whole database is costly

    Evaluating every stored resume against every new job spends credits on profiles nobody will review.

  • 01

    The job as the query

    Send a stored job_id, or the job text, which is stored on the way as Job Criteria Extractor would store it.

  • 02

    Closest resumes first

    Up to 500 application_ids, ranked by similarity to the job, 50 by default.

  • 03

    City and radius

    Keep the resumes within 1 to 500 km of a city, 30 by default, with a country code when the city name exists in several countries.

  • 04

    Recent resumes only

    added_after keeps the resumes added after a date, to focus on recent applicants.

  • 05

    Already scored, flagged

    already_scored tells which resumes are scored, or being scored, for this job; scoring them again costs nothing, unless a score is stale or its verdict was reset.

  • 06

    One pool per client company

    The search covers the resumes of one HireLayer-Workspace, so each customer’s pool stays apart.

Search first, then score

PropertyTalent Pool SearchResume Scorer
Question answeredWhich stored resumes are closest to this job?How well does each resume meet the job?
Looks atEvery resume of the workspaceThe resumes you send
Per resumeapplication_id · similarityscore · verdict · criteria
ExplanationNoneA quote and a sentence per criterion
Credits1 per search1 per resume evaluated

Search the talent pool for one job

Values below come from the API reference example. Field names and shapes match the live contract.

RequestPOST /api/v4/resumes/search
curl -X POST https://hirelayer.co/api/v4/resumes/search \
  -H "X-API-Key: $HIRELAYER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "job_id": "job_020cb8c5f1f8eb650cec00dc3d90f8ea",
    "limit": 50,
    "filters": {
      "location": { "city": "Paris", "country_code": "FR", "radius_km": 30 },
      "added_after": "2026-01-01T00:00:00Z"
    }
  }'
Response200 OK · application/json
{
  "job_id": "job_020cb8c5f1f8eb650cec00dc3d90f8ea",
  "results": [
    {
      "rank": 1,
      "application_id": "file_d7e21d373637a897b17b8fdf63122807",
      "similarity": 0.57,
      "already_scored": true
    }
  ],
  "credits_used": 1
}
results[].similarity
Closeness to the job, from 0 to 1. Compare it within one search only: it is not a score.
results[].already_scored
true when the resume is already scored, or being scored, for this job: scoring it again costs 0, unless its score is stale or its verdict was reset.
filters.location
city, radius_km (30 by default) and country_code. Resumes with no known location are left out.
credits_used
1 per search, whatever the number of results.

Where teams search their talent pool

HireLayer Talent Pool Search is used by recruiting software and recruiting services. Each use case links to the full workflow.

  1. 01

    Talent rediscovery

    When a job opens, search the resumes you already hold and invite the closest past applicants to apply before you post.

    Talent Pool Search for ATS platforms
  2. 02

    Shortlist from a sourcing database

    Search the profiles saved in your sourcing product, then score the top ones against the job for the recruiter.

    Talent Pool Search for Sourcing tools
  3. 03

    Fill a job order from the pool

    Find the closest candidates within 30 km of the client site, then score them before the first call.

    Talent Pool Search for Staffing & temp agencies

Integrate talent pool search in your sourcing flow

Call the API from your backend and keep the key server-side. Your product keeps its records, interface and review process.

  1. STEP 01

    Build the pool

    Parse resumes with HireLayer Resume Parser, or score them once: every resume sent to the API is stored in the workspace.

  2. STEP 02

    Search with the job

    Send the job_id, with a location or a date filter when the job needs one.

  3. STEP 03

    Score the ones you pick

    Send the top application_ids with the job_id to HireLayer Resume Scorer for the score, the verdict and the evidence.

Technical specifications

Authentication
X-API-Key header
Content-Type
application/json
Job
job_id, or job with its text, stored on the way
limit
1 to 500, 50 by default
Filters
location (city, country_code, radius_km 1–500) · added_after
Output
rank · application_id · similarity · already_scored
Scope
The resumes of the HireLayer-Workspace sent
Billing
1 credit per search

No backend to write? Use Talent Pool Search from ChatGPT, Claude or your ATS.

Where Talent Pool Search fits in the HireLayer pipeline

Each product works on its own. Chain them when a workflow needs CV data, job criteria, a search and a decision aid together.

  1. CV filePDF, DOCX, image…
    Resume ParserResume Parsing API→ application_id · resume
    Job RecommendationsJob Recommendation APIresume → closest open jobs
    Resume ScorerCandidate & Job Matching APIjob + resumes → score · verdict
  2. Job descriptionText or file
    Job Criteria ExtractorJob Parsing API→ job_id · criteria[]
    Talent Pool SearchTalent Pool Search APIjob → closest stored resumes
    Resume ScorerCandidate & Job Matching API+ precise_ranking → ranking_reason
  3. Free-text skillsFrom CVs, jobs or users
    Skills NormalizerSkills Matching API→ taxonomy skill ids

    Store skill ids on profiles and jobs for search and facets.

Resume Parser and Job Criteria Extractor store what they read. The searches find the closest resumes or jobs; Resume Scorer explains the fit. One API key and one credit balance cover every call.

Talent Pool Search API questions

Answers based on the current API contract.

Which API searches my own resume database to find the best candidates for a new job?

HireLayer Talent Pool Search does. Send the new job, as a stored job_id or as its text, to POST /api/v4/resumes/search: it searches the resumes already in your HireLayer workspace and returns up to 500 application_ids, closest to the job first, filtered by city and radius or by date added when you need it. There is no separate index to build: every resume parsed with Resume Parser or scored with Resume Scorer is searchable. Then send the ones you pick to Resume Scorer for a score and the evidence for each criterion. A search costs 1 credit.

What does Talent Pool Search return?

Resumes from your own database, closest to the job first: each with its application_id, a rank, a similarity from 0 to 1 and already_scored. There is no explanation. Send the resumes you choose to Resume Scorer to get a score, a verdict and evidence for each criterion.

Which resumes does it search?

The resumes stored in the workspace named by the HireLayer-Workspace header: every resume parsed with Resume Parser, scored with Resume Scorer or sent to Job Recommendations. Each client company can have its own workspace, and a search never crosses them.

Is similarity a matching score?

No. similarity says how close a resume is to the job compared with the other results of the same search. It does not check criteria and cannot be compared from one search to another. The score that says how well a resume meets the job comes from Resume Scorer.

How does the location filter work?

Give a city and, when the name exists in several countries, a country_code such as FR. Resumes within radius_km of it are kept, 30 km by default and up to 500. Resumes whose location is unknown are left out when the filter is set.

Can I search with a job that is not stored yet?

Yes. Send job with its text instead of job_id: the job is stored, as Job Criteria Extractor would store it, and the answer gives its job_id for the next calls.

Can I use Talent Pool Search for talent rediscovery?

Yes, it is built for it. Talent rediscovery means looking at the candidates already in your database before sourcing new ones. When a job opens, send it to Talent Pool Search: the resumes received for earlier jobs come back closest to the new job first, and already_scored shows which ones were already evaluated for it. Add added_after to keep recent applicants only, or a city and radius for an on-site role.

How is Talent Pool Search billed?

1 credit per search, whatever the number of results. Scoring the resumes you pick is billed by Resume Scorer: 1 credit per resume, 0 for one already scored for the job.

Make your first call to HireLayer Talent Pool Search today.

Create an account to get an API key. Credits are shared across all six HireLayer products.