Verification question
Use verification questions to collect employer or institution responses beyond core verification fields (dates, title, degree, and similar). Define questions on each search when you create an order. Answers are returned on terminal webhooks after the verifier completes the form. Attach questions viasearchTypes[].verificationQuestions. See Search type.
- Define custom questions on each relevant
searchTypes[]entry at order creation. - SNH AI sends a form (PDF and/or online questionnaire link) that includes your custom questions and standard employment or education fields.
- Responses are extracted from the returned form.
- On
verification.completed, answers appear indata.verificationQuestions. Incomplete or invalid required answers escalate viaverification.action_requiredinstead.
Questions are defined at order creation only. You cannot add or change questions after the order is submitted.
Fields
Send these fields when creating an order. Do not sendfieldKey, origin, or conditionMet — the platform assigns those.
Validation limits
Invalid payloads return
400 Bad Request. See Errors.
Question types
Type-specific rules
For
single_select and multi_select, matching is case-sensitive against options[].value. Align webhook parsing with those values. Only set minSelections when the question is also required: true — otherwise a blank optional multi_select can fail validation on PDF, fax, or voice inbound.Conditional questions
Optionalcondition attaches a one-level dependency on an earlier question:
Allowed parent types:
yes_no, single_select, checkbox, numeric, rating_scale (not free_text or multi_select).
Nesting: One level only — a parent that itself has a condition is rejected.
Semantics after extraction:
- Parent matches →
conditionMet: true;requiredapplies if set. - Parent does not match →
conditionMet: false; childselectedAnsweris cleared tonull.
Ordering
- Display order follows the array order of
verificationQuestionsin the request. - The resolved form shows standard questions first, then custom questions in request order.
Response fields (webhook)
Each question in webhook payloads includes the request fields plus:Where responses appear
Prefer
data.verificationQuestions for most integrations. Use data.questionnaire when you need schema version and search type in one object.
Incomplete or invalid answers
On PDF, fax, and voice inbound paths:
These paths emit
verification.action_required with reasonCode: HUMAN_ESCALATION and do not emit verification.completed.
Standard questions
SNH AI prepends standard questions for the search type. StandardquestionId values use a reserved range (700001+). Custom questionId values must not collide with a standard ID for that search type — order creation returns 400 if they do. Standard question definitions cannot be overridden.
Employment (searchType: "EMPLOYMENT")
reason_for_leaving and employment_status have allowComment: true.
Education (searchType: "EDUCATION")
All education standard questions are optional (
required: false) with allowComment: false.
Questionnaire envelope
Whendata.questionnaire is present:
Example
Custom questions on order creation
condition.dependsOn: 700001 targets the standard employment eligible_for_rehire question.
Webhook response (verification.completed)
questionnaire.questions is abbreviated as [] above. In production it matches data.verificationQuestions.Escalation (verification.action_required)
Validation rules
- Stable IDs — Reuse the same
questionIdacross orders for correlation. CustomfieldKeyis derived from the prompt; changing the prompt changesfieldKey. - Unique
questionId— Must be unique within eachverificationQuestionsarray and must not collide with standard IDs (700001+). - Pre-fill — Set
selectedAnswer/commentat order creation when known. The verifier may still change values on the form. - Parsing — Index by
fieldKeyfor standard questions and byquestionIdorfieldKeyfor custom. Useoriginto distinguish them. Treatmulti_selectanswers as arrays. multi_selectanswers —selectedAnsweris astring[]for this type only. Other types remain strings (ornull).
Related schemas
- Search type — Where
verificationQuestionsattaches to each search - Create order — Full request body reference
- Webhook events —
verification.completedandverification.action_required - Webhook integration — Delivery, signatures, and retries

