Skip to main content
POST
Free. Use Parse to show users how their request was understood, let them edit it, or build a filter UI on top of natural language. When nothing blocks the search, search_request is a ready body for POST /people/search: send it as-is, or edit it first. Otherwise search_request is null, and unsupported_criteria or errors say what to change. Parse runs no search and spends no credits.

Headers

string
A unique string for this request, 1 to 255 characters. Retrying with the same key and body returns the original response instead of starting new work. Reusing a key with a different body returns 409 idempotency_key_reused. Always send one when starting a search.

Body

string
required
The request to parse, from one sentence to a pasted paragraph of requirements.Maximum 1,000 characters.

Response

200 How the query was read.
string
required
company_search_parse or people_search_parse.
string
required
The original text.
object | null
required
The structured reading of the query. null when nothing in the query maps to a structured field.
object[]
required
Requirements that will be checked against evidence for each candidate.
string[]
required
Requirements no public source can confirm, quoted from the query, such as visits to your own website or subjective quality. The search cannot run while there are any.
object[]
required
Ambiguous wording and how it was read. Assumptions do not block the search.
object[]
required
Problems validating the filters the query was read as.
object | null
required
A ready request body for the matching search endpoint. null when unsupported_criteria or errors is not empty, or the query gave nothing to search on.

Errors

Every error uses the same shape. See Errors.