Match one source document against the user's ALREADY-INDEXED corpus and return the
best-matching, ranked candidates (RChilli Search & Match Engine). Requires a populated index.
Uses RChilli's purpose-built matching engine — more reliable than manually comparing documents.
Use this when the user wants to: find the best/top matching resumes for a JD, find
matching candidates from their pool, or rank their indexed resumes/JDs against a given
document — e.g. "find the best candidates in my database for this job".
Also phrased as: shortlist from my pool, top matches for this JD, rank my candidates.
Do NOT use for: scoring a single resume against a single JD with no index
(use ``search_one_match``); plain keyword lookup (use ``search_simple_search``).
Supports all four match directions by combining ``index_type`` and ``doc_type``:
- **JD to Resume** — ``index_type='Resume'``, ``doc_type='JD'``:
Search the Resume index using a JD as the source document.
- **Resume to Resume** — ``index_type='Resume'``, ``doc_type='Resume'``:
Search the Resume index using a Resume as the source document.
- **Resume to JD** — ``index_type='JD'``, ``doc_type='Resume'``:
Search the JD index using a Resume as the source document.
- **JD to JD** — ``index_type='JD'``, ``doc_type='JD'``:
Search the JD index using a JD as the source document.
The ``document_text`` is automatically parsed using the RChilli Resume or JD parser
(driven by ``doc_type``), and the resulting structured JSON is base64-encoded
and submitted as the match source — no manual encoding is required.
Args:
index_type: Index to search — ``Resume`` (default) or ``JD``.
index_key: Same as ``userkey`` — the RChilli API user key. Leave blank;
the authenticated session userkey is injected automatically.
doc_type: Type of the source document — ``Resume`` (default) or ``JD``.
This determines which parser processes ``document_text``.
document_text: Plain-text content of the source document.
Parsed and encoded to base64 JSON internally.