| Organization (also Customer) | The company using the SNH AI platform. API data is isolated per organization. |
| User | An individual who accesses the platform (dashboard or support workflows). |
| Theary | Product/platform name used in URLs and some technical headers (for example webhook User-Agent). Same product as SNH AI Verification. |
| JWT / Bearer token | Authentication token SNH AI issues for API access. Send it as Authorization: Bearer <token>. |
| API credentials | Auth material issued by SNH AI. For Verification, this is typically a Bearer JWT (not a long-lived static API key). |
tenant claim | JWT field that carries your organization identifier. Required on protected Verification routes. |
| Applicant | The person whose employment or education history you are verifying. |
| Business context | Hiring context for the role (employer, title, worksite, salary) submitted with the order. |
| Request | An API submission from your system to SNH AI. |
| Order | A Verification container created by POST /orders. Holds applicant data and one or more searches. |
| Batch | A non-durable grouping of orders submitted via one POST /batches call. Creation runs all orders in parallel with no atomicity guarantee (partial success is possible); there is no persisted batch entity — track and cancel work with order endpoints. See Batches API. |
| Search | A unit of verification work (EMPLOYMENT or EDUCATION) under an order. |
| Activity | Operational progress on a search (attempts, inbound, status). Visible when you fetch a specific search. |
| Contact plan | The set of researched contacts and channels SNH AI plans to use for outreach on a search. |
| Outbound | Messages SNH AI sends to employers or schools (email, fax, or voice). |
| Inbound | Responses SNH AI receives from employers, schools, or upstream systems. |
| Channel | Communication path used for outbound or inbound (for example EMAIL, VOICE, FAX). |
| Closeout | Terminal completion of a search, including the result payload and related webhook delivery. closeoutEndpoints routes those events. |
| Result | Completed verification output, usually delivered on verification.completed. |
| Webhook | HTTPS callback from SNH AI to your system for status and outcome events. |
verification.completed | Webhook event for a terminal verification outcome. |
verification.action_required | Webhook event when automation needs manual follow-up or escalation. |
verification.notification | Webhook event for intermediate progress (contact plan, outbound attempt, inbound message). |
| Questionnaire | Optional online form URL/access code you can attach to a search for the applicant. |
| Signed release | Optional signed release PDF attached to outbound verification requests. |
| Sandbox | Non-production environment (https://sandbox.theary.ai) for integration testing. |
| Production | Live environment (https://api.theary.ai). Confirm the production base URL SNH AI issues with your credentials. |
| External search ID | Your correlation ID (externalSearchId) echoed on searches and webhooks. |
| Third-party vendor | An external verification portal (for example The Work Number or NSCH) that may be required or banned per search. |
| Third-party ban | Per-search list of vendor codes that must not receive routing or third-party webhooks for that search. |
| SLA | Service-level target for how long a search may run before escalation. |
| Escalation | Hand-off to human review when automation cannot finish within policy. |
