Core concepts
This page explains the Verification workflow from the customer’s perspective: how you start work, how SNH AI processes it, and how you receive outcomes.What Verification does
The Verification service automates employment and education verification. You send applicant and history data. SNH AI researches contacts, performs outbound outreach, processes inbound responses, and returns structured results.Order → Search → Result
One order can contain multiple searches (for example employment and education together). Each search progresses independently.
Status lifecycle
Orders and searches each have a status that progresses through a defined set of values.Order status
Search status
Verification result outcomes
When a search completes, theverificationResult.outcome field contains one of:
Additional outcomes may be introduced as the platform expands. For forward compatibility, treat any unrecognized outcome as requiring manual review.
How you get responses
- Create response (sync):
201withverificationOrderIdandsearchIds— the order was accepted, not finished. - Webhooks (async, preferred): Configure
webhookConfigon the order or rely on organization defaults. VerifyX-Webhook-Signature. - Polling (async fallback): Use
GET /orders/{id}/searchesfor search status and verification results. UseGET /orders/{id}/searches/{searchId}when you also need activity history. UseGET /orders/{id}only for order-level status — its nestedsearchlist is a summary and does not include results.
Batch vs single order
- Single order:
POST /background-check/v1/orders— primary integration path. - Batch:
POST /background-check/v1/batchessubmits many orders in one HTTP call. Each order is independent — record everyverificationOrderIdand track work with order endpoints. See API overview.

