Documentation Index
Fetch the complete documentation index at: https://documentation.theary.ai/llms.txt
Use this file to discover all available pages before exploring further.
Integration patterns
Each snippet focuses on the differing parts of a Create order request. Combine with full field requirements from Applicant, Business context, History, and VerificationRequest.Employment-only
Education-only
Employment and education on one order
applicant and businessContext as for a single-type order.)
Known contacts / skip broad research
UsedefaultSearchConfig or per-search searchConfig with research.skipResearch: true and seed outbound.contactHints. See Search config.
Email-only outreach
Manual review (inbound)
Per-search webhook routing
Use WebhookTarget objects undercloseoutEndpoints and fallbackEndpoint (string URL, single object, or array). Example: send employment closeouts to one URL and everything else to a fallback:
Release-form upload
GET /files/release-form/generate-upload-url→signedUrl,fileUriPUTPDF tosignedUrl- Set
applicant.signedReleaseFileUrltofileUri(gs://...)
Batch create caveats
POST /background-check/v1/batches accepts { "orders": [ ...VerificationRequestDto ] } and creates each order in parallel via the same path as single-order creation. The response includes a synthetic batchId and per-order verificationOrderId / searchIds in orders.
Validation / creation errors: if any order fails validation or throws during createOrder, the whole HTTP request fails with an error (you do not get a 200 with mixed success/failure).
Partial success risk: if the server fails after some orders were created (timeout, connection drop), you can be left with some orders already persisted. Persist every returned verificationOrderId as soon as you receive the response and reconcile with List orders.
Not implemented: listing batches, fetching a batch by id, and deleting a batch return placeholder payloads; track orders with List orders, Get order, and Get order searches.
Webhook idempotency
Deliveries may retry. Deduplicate with theX-Event-Id header (unique per delivery) and your own externalSearchId when you set it on searches. Acknowledge with a 2xx response; see Webhook events and Webhook integration.