Free demo hits. Pay when you go live. Request access
Contact & Address

Digital Address Verification API

Send a link; the person captures photos of their home, nameplate and surroundings from the address itself. Location, time and device signals are checked for spoofing, the images are analysed and the result is a verified address with evidence, in hours instead of the days a field visit takes.

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

    • Person's name and contact for the capture link*
    • Declared address*
  2. emver API

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

  3. Completed via

    Geo-tagged capture on the person's phone

  4. You receive by webhook

    • Verification outcome
    • Distance between declared and captured location
    • Photo evidence with GPS and timestamps
    • Anti-spoofing checks
    • Reviewer notes where applicable
digital-address-verification Full reference
Overview

What the Digital Address Verification API does

Physical address verification is slow and expensive. Digital Address Verification puts the capture in the person's hands and the anti-spoofing in ours: GPS and timestamp checks on every photo, detection of static or drive-by captures, landmark and nameplate analysis, and a reviewer queue for anything borderline.

The outcome arrives by webhook with the evidence pack, and can escalate to a physical visit through emver when the digital result is inconclusive.

Consent is part of the contract

The person captures the evidence themselves after consenting to location and photo collection; the consent record is stored with the case.

Benefits

Why teams use the Digital Address Verification API

Verify a residential address with geo-tagged, timestamped photos captured by the person.

Hours, not days

No scheduling a field visit.

Anti-spoofing built in

GPS, time and image checks catch fake captures.

Fraction of field cost

Reserve physical visits for exceptions.

Async

Result and evidence post to your webhook.

Use cases

Where it's called

Where the Digital Address Verification API is typically called, and what it settles there.

Employee background checks

Current and permanent address for the personnel file.

Gig partner onboarding

Verify the address riders operate from.

Lending

Address proof for loan files without a visit.

Tenant screening

Confirm previous residence.

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

Digital Address Verification API: frequently asked questions

What teams ask before adding the Digital Address Verification API to their integration.

The link stays valid for the window you set and reminders are sent automatically. If they cannot capture, escalate to a physical verification.

Each photo carries GPS and time metadata that is checked against the declared address and the capture session; static images, screenshots and drive-by captures are detected and flagged.

Related

APIs that run alongside it

Usually called with the Digital Address Verification 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.