Pre-filled answers (selectedAnswer)
Set selectedAnswer on a custom question when you already know the likely answer. If the verifier leaves that question blank, the pre-filled value is the answer you receive. If the verifier answers it, their answer replaces yours. Standard questions cannot be pre-filled.
Pre-fills are sent on Create order, inside searchTypes[].verificationQuestions[]. For the full question schema, see Verification question.
Before you start
Value shape by question type
selectedAnswer is a string for every type except multi_select, which takes an array of strings. Numbers and booleans are never accepted, including for numeric, rating_scale, and checkbox.
What comes back on the webhook
Answers arrive indata.verificationQuestions on verification.completed. See Webhook events.
The same rules apply to answers from an earlier reply. If one reply checks
dental and a later copy of the form comes back with nothing checked, the answer stays ["dental"].
Examples by type
Each example is one entry insearchTypes[].verificationQuestions[], followed by the webhook selectedAnswer for a blank return and for a verifier who answers.
free_text
Spaces are kept exactly as sent. A value made only of spaces counts as blank, so it does not satisfy
required.
single_select
You can send the optionlabel. It is stored as the option value, and the webhook always returns the value.
multi_select
Send exactoptions[].value strings in an array. Labels and case variants are rejected.
A non-empty pre-fill must respect
minSelections and maxSelections. With maxSelections: 2, ["health", "dental", "vision"] returns 400. Repeated values count once, so ["health", "health"] is one selection.
An empty array ([]) is accepted and behaves like no pre-fill, even when minSelections is set.
rating_scale
" 04 " is accepted and stored as "4". 4, "4.0", "4 stars", and values outside the scale return 400.
yes_no
"Y", "true", and "Maybe" return 400. To allow an “unsure” answer, use single_select with an Unknown option instead.
numeric
Anumeric pre-fill is a string, such as "40", "-5", "0", or "37.5". A JSON number like 40 is rejected.
Only your pre-fill must be a plain decimal string. A verifier’s answer is returned as written, so it can include units such as
"20 hours". A verifier answer that does not start with a number escalates instead of completing. Parse the leading number in your own code.checkbox
A checkbox is an attestation, so the returned form always decides it. An unchecked box is reported as
"false" even over a "true" pre-fill, because the verifier never saw your pre-fill and did not confirm it. The pre-fill only stands when the verifier answers some other way, such as an email reply without the form.
"True", "TRUE", "yes", "1", and true return 400.
Full order example
All seven types on one employment search:verification.completed are:
fieldKey, and every request field on each question. Match answers to your questions by questionId.
Interactions with other question settings
required
A non-blank pre-fill satisfies required. If the verifier skips a required question that has a pre-fill, the search can still complete with your pre-fill. It does not escalate as MISSING_REQUIRED_INFORMATION. Leave selectedAnswer unset on questions the verifier must answer themselves.
These pre-fills do not count as answered:
null""- a string made only of spaces
[]
checkbox value of "false" does count as answered.
condition
A conditional question only keeps an answer while its condition is met. When a reply is processed and the parent’s answer does not match condition.values, the child’s selectedAnswer is cleared to null, including your pre-fill. This also happens when the parent is left unanswered.
To keep a child’s pre-fill, pre-fill its parent with a matching value as well.
allowComment and comment
A comment pre-fill follows the same rules as selectedAnswer: a blank comment box keeps it, and a written comment replaces it. When allowComment is false, a comment is still accepted and returned, but the form has no comment box, so the verifier cannot change it.
Standard questions cannot be pre-filled
Standard questions, such as700001 eligible_for_rehire, cover the core verification fields: rehire eligibility, reason for leaving, dates, and position. Their answers always come from the verifier. A selectedAnswer or comment on a standard question returns 400.
This keeps the verifier’s answer and the question in agreement. A verifier can answer rehire eligibility in an email or on a call, and that answer is returned in the verified data (verifiedRehire). It is not written to the standard question, so a pre-fill there could report your value next to a different answer from the verifier.
To record something you already know about a standard field, add a custom question for it.
Validation errors
An invalid pre-fill returns400 Bad Request, and no order is created. See Error handling.
Checklist
- Send
numeric,rating_scale, andcheckboxpre-fills as strings. - Send
multi_selectpre-fills as an array of exact option values, insideminSelectionsandmaxSelections. - Leave
selectedAnswerunset on required questions the verifier must answer themselves. - Pre-fill a conditional question’s parent as well as the child.
- Set
allowComment: truewhen you send acomment. - Pre-fill custom questions only. A pre-fill on a standard question returns
400. - Read
selectedAnswerbytype: astring[]formulti_select, a string ornullfor everything else.

