Verifications API

Updated:

Unified.to's Verification API lets your application order identity, background, employment and other checks from verification providers, track each check's status and read its result. It uses two objects: a package is a check a provider offers, and a request is one ordered check with its result. It's available on every plan.

Which integrations does it support?

Verification providers including Checkr, Certn, First Advantage, Socure, Sterling Check, Trulioo, Verifiable and Yardstik. See supported integrations for the full list and each integration's Feature Support tab for its methods, fields and webhooks.

Objects and methods

ObjectMethodsVaries by integration (as of 19 October 2026)
PackageList, RetrieveRead-only on every integration. Retrieve on Accurate, Checkr, Harver, IDfy, IDmission, Socure and Verified First. SambaSafety, Tazworks and Verified Credentials have no package object.
RequestCreate, List, Retrieve, Update, RemoveCreate on every integration except Makesure. Retrieve on all except Socure and Verified First (create only). List on Accurate, Certn, Checkr, Harver, Makesure, TrustID, Verifiable, Yardstik and Zinc. Update on Certn, Checkr and Yardstik. Remove on Checkr, TrustID, Verifiable, Yardstik and Zinc.

An operation an integration doesn't support returns 501.

MethodPathOperation
GET/verification/{connection_id}/packageList packages
GET/verification/{connection_id}/package/{id}Retrieve a package
POST/verification/{connection_id}/requestCreate a request
GET/verification/{connection_id}/requestList requests
GET/verification/{connection_id}/request/{id}Retrieve a request
PUT/verification/{connection_id}/request/{id}Update a request
PATCH/verification/{connection_id}/request/{id}Update a request (partial)
DELETE/verification/{connection_id}/request/{id}Remove a request

List requests accept limit, offset, sort, order, updated_gte, query, package_id, candidate_id, fields and raw; which filters an integration honours is on its Feature Support tab (Harver requires candidate_id). Connection permissions: verification_package_read, verification_request_read, verification_request_write.

How does a check work?

  1. List packages on the connection. Each package has a type (identity verification, screening, background check, employment, education, credit check, fraud prevention, other) and the parameters the check needs; some also carry valid_regions, cost_amount or average_processing_times where the provider supplies them.
  2. Create a request with the package_id, the person's profile (profile_name, profile_emails, profile_date_of_birth, profile_addresses and so on) and, optionally, a candidate_id pointing to an ATS candidate.
  3. Read the result on the same request: response_status (PENDING, PASSED, FAILED, COMPLETED), response_score, response_details and response_download_urls, depending on the integration. Where the provider collects consent or details from the candidate on its own page, the request carries response_redirect_url.

Result fields are read-only. How long a check takes depends on the provider and package.

Webhooks

Subscribe to the verification_request object for created and updated events (results and status changes arrive as updated; deleted on Yardstik only). verification_package events are available on Checkr only. As of 20 October 2026:

  • Native: Accurate, Checkr, SambaSafety, Sterling, Sterling Check, Tazworks, TrustID, Verified First, Yardstik and Zinc.
  • Virtual (virtual webhooks check at an interval you set, as often as every minute on paid plans): Verifiable, TrustID, Yardstik and Zinc.
  • None: Certn, First Advantage, Harver, IDfy, IDmission, Makesure, Socure, Trulioo and Verified Credentials. Retrieve the request instead.

Slow fields

None documented for verification objects.

Data handling

Each request goes to the provider when you make the call. Unified.to keeps no customer records at rest; connection credentials and operational metadata are encrypted at rest. Store any results you need in your own systems.

See also

Run In Postman

Data Model

VERIFICATION data model

SVG fallback viewer

Loading diagram...
Share
Are we missing anything? Let us know
Was this page helpful?