Search input
Choose how users provide search intent
Input quality has the strongest influence on search quality. Good input is specific, structured, observable on a professional profile, and free of contradictions.
The hiring manager is the source of truth. Before searching, they should approve the target profile and business context, 2–6 real must-haves, nice-to-haves, and exclusions. A recruiter, integration, or LLM can structure the request, but should not silently choose essential criteria or trade-offs.
- Requirements first (recommended): Users enter structured
search_requirementsand review them before searching. They can see each criterion, mark must-haves and nice-to-haves, and resolve conflicts before spending credits. This gives them the most control. - Query, review, then rerun: Users start with a natural-language
query. Pearch converts it intosearch_requirements. Show those requirements for human review, then rerun the search with the approved criteria. This balances a simple input experience with explicit control. - Query only: The search runs without a review of the interpreted requirements. This is supported but offers less control: vague, unstructured, or contradictory queries can lose important distinctions.
When you supply both fields, search_requirements takes precedence. Use POST /v2/search for people and company and lead search when you want companies and people associated with them.
Before increasing the result limit, review the requirements, check any filters, and choose a search mode. Start with a small run in the API Playground.
Updated 23 minutes ago
