Free demo hits. Pay when you go live. Request access
Workforce & Assets

Employment Verification (Employer Confirmation) API

Where EPFO data ends, emver's verification desk contacts the employer's HR through verified channels and returns confirmed tenure, designation, last drawn salary band and eligibility for rehire, delivered through the API with a tokenised status link.

Response
Async, by webhook
Inputs
3 required · 4 optional
Consent
Recorded per request
Billing
Per successful call
POST /v1/employment-verification
Sandbox · Production
  1. Your application sends

    • Candidate name*
    • Employer name*
    • Employee ID
    • Tenure from*
    • Tenure to
    • Designation
    • Supporting documents
  2. emver API

    Issues a hosted consent link, tracks the person's authorisation and assembles the result.

  3. Completed via

    Authoritative source

  4. You receive by webhook

    • Request ID
    • Verification status
    • Tenure confirmed
    • Designation confirmed
    • Exit reason
    • Eligible for rehire
    • Report link
employment-verification Full reference
Overview

What the Employment Verification (Employer Confirmation) API does

This is an asynchronous check. Submit the candidate's consent, employment details and documents; the request is processed by emver's verification team and the API reports each status change until the employer's confirmation is recorded.

Consent is part of the contract

The candidate authorises emver to contact previous employers; the consent record accompanies every request.

Benefits

Why teams use the Employment Verification (Employer Confirmation) API

Direct confirmation of tenure, designation and exit reason from the previous employer.

Human-verified

HR confirmations from verified contacts, not database guesses.

API-delivered

Status updates and the final report through the same integration.

Use cases

Where it's called

Where the Employment Verification (Employer Confirmation) API is typically called, and what it settles there.

Pre-employment screening

The standard employment component of a BGV package.

Executive hiring

Confirm senior tenures where records are thin.

How it works

Four steps, one response envelope

Request and response details, environments and a ready-to-import collection are in the developer console.

  1. 01

    Authenticate

    Call with your organisation API key. Sandbox and production use the same contract.

  2. 02

    Create the consent link

    Send the person's details and the documents you need. You receive a hosted link to share on any channel.

  3. 03

    The person authorises

    They sign in and choose what to share. Nothing moves without their approval.

  4. 04

    Receive the result

    Verified documents and details arrive by webhook or on the status endpoint.

Privacy and security built in

Consent recorded · Payloads not retained beyond your retention window · Every request traceable

FAQ

Employment Verification (Employer Confirmation) API: frequently asked questions

What teams ask before adding the Employment Verification (Employer Confirmation) API to their integration.

Typically two to five working days depending on employer responsiveness; the status link shows progress in real time.

Related

APIs that run alongside it

Usually called with the Employment Verification (Employer Confirmation) API, on the same key.

All APIs
Access usually set up within one working day

Start verifying with emver today.

Tell us which APIs and what monthly volume. We set up your organisation, approve the APIs with demo hits and share per-call pricing.