Submit feedback on how a search read the request

Report problems with the requirements a search ran on rather than with a profile:
a requirement that is ambiguous, bundles several conditions, has the wrong
must-have setting, was added although the request did not ask for it, or misreads
the request, plus what the request asked for that no requirement covers.

Identify the search with the /v2/search response's thread_id and, optionally,
its uuid as search_id. flags[].requirement_index is the position of a
requirement in search_requirements_stats; Pearch stores a snapshot of those
requirements with the feedback and returns it as requirements.

There is one entry per thread and each submission replaces it, whoever sends it.
Requirements without codes or a note are not stored.

Body Params
uuid
required

The thread_id returned by /v2/search.

uuid | null

The uuid returned by /v2/search. Optional; defaults to the thread's latest completed search.

flags
array of objects
length ≤ 50

Problems with individual requirements; each requirement at most once.

flags
missing_requirements
array of strings
length ≤ 20

What the request asked for that no requirement covers.

missing_requirements
string
length ≤ 2000
string
enum
Defaults to person
Allowed:
Responses

400

Invalid values, unknown codes, or a requirement index outside the search's requirements

401

Invalid API key

403

Invalid API key

404

No completed search in the thread, or none with this search_id

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json