Identity Verification API - Global KYC, AML and Age Checks

Verify a person against government registries, credit bureaus, telco records and electoral rolls in more than 100 countries, and screen them against global sanctions, PEP and adverse media watchlists, from one input list.

What this actor does

• Electronic identity verification (eIDV) against official government and commercial data sources, country by country.
• AML watchlist screening against sanctions lists, politically exposed persons, their relatives and close associates, special interest persons and entities, and adverse media, drawn from over 100,000 sources in 40 or more languages.
• Age verification derived from the date of birth the sources hold, for onboarding flows with an age gate.
• Address verification and cleansing, returning which address elements matched rather than a single yes or no.
• Composite and sequenced searching, so several services can answer for one person in a single call.
• Safe harbour reporting, with the safe harbour score and outcome carried on every row for audit.
• One row per service result, with the provider's own match scores, the exact identity elements that matched, and the reporting reference their support asks for.

Input

Fill in the people list, choose a country and name the services to run. Every field is optional except the ones the provider needs to match on: a name or an identifier, plus a country and a service.

{
  "countryCode": "AU",
  "services": ["Australia Residential Lookup"],
  "people": [
    {
      "firstName": "Aloysius",
      "lastName": "Pasco",
      "dateOfBirth": "1946-11-01",
      "addressElement1": "30 Plane Tree Green",
      "addressElement3": "Forrestfield",
      "addressElement4": "WA",
      "addressElement5": "6058",
      "identityVariables": { "phoneNo": "0487787402" }
    }
  ],
  "username": "YOUR_ACCOUNT_USERNAME",
  "password": "YOUR_ACCOUNT_PASSWORD",
  "maxResults": 100
}

Example output

{
  "service": "Australia Residential Lookup",
  "matchStatus": "Full Match 1+1 Verification",
  "searchStatus": "Successful",
  "identityVerified": true,
  "status": 1,
  "sourceStatus": "Successful",
  "nameMatchScore": "A1",
  "addressMatchScore": "0",
  "safeHarbour": false,
  "safeHarbourScore": "N/A",
  "verifiedElements": ["addressElement1", "addressElement3", "addressElement4", "addressElement5", "dateOfBirth", "firstName", "lastName", "mobileNumber"],
  "verifications": { "firstName": true, "lastName": true, "middleName": false, "dateOfBirth": true, "mobileNumber": true, "landlineNumber": false },
  "returnedData": { "source": "DZ1" },
  "watchlistResults": null,
  "countryCode": "Australia",
  "clientReference": "Test_0001",
  "reportingReference": "DZ-7905e55c-0ebf-4857-9958-878642e720bc",
  "found": true
}

Frequently asked questions

What is an identity verification API?

An identity verification API checks that a person is who they say they are by matching the details they gave you, such as name, date of birth, address and phone number, against authoritative data sources like government registries, credit bureaus, electoral rolls and telco records. It returns a match result per element rather than a single score, which is what anti-money laundering and know your customer rules require you to record.

Which countries does this actor cover?

More than 100. The provider selects data sources by country, so the country code decides which services are available: Australian services include the residential file, credit bureau, driver licence, passport, Medicare card, electoral roll and superannuation, while other regions expose their own equivalents across APAC, EMEA and the Americas. Watchlist screening is global and is called with the country set to All.

What is AML watchlist screening?

AML watchlist screening checks a person or entity against sanctions lists, politically exposed persons and their relatives and close associates, special interest persons and entities, and adverse media reporting. This actor returns each hit with its category, scan id and a link to the provider's detailed report, so a compliance analyst can review the match rather than trusting a single flag.

What is a safe harbour score?

Safe harbour is a regulatory standard, used in Australia among others, that treats an identity as verified when a defined combination of identity elements has been matched against independent sources. Every row carries the safe harbour outcome and the score behind it, so the evidence for a decision is stored alongside the decision.

Does a no match cost anything?

No. This actor charges only for service results that carry a verification outcome. Records refused before they were sent, records the provider would not process, and results that came back with no match at all are stored in the dataset but are not charged for.

Do I need my own account?

Yes. This is a bring your own credentials actor: it calls the API with your own account username and password, which are exchanged once per run for a session token. Nothing is shared between runs and the credentials are never written to the dataset. The services you can call are the ones your contract covers.

Can I test without spending live credits?

Yes. Set the environment to sandbox, which checks against the provider's test identities rather than live data. Sandbox credentials are a separate account from production, so use the pair issued for that environment.

How is personal data handled?

The actor sends only the fields you put in the people list, and stores only what the provider returns. Some data sources require the individual's consent before they may be queried, and it is your responsibility to hold that consent and to use a permissible purpose, as your contract with the provider sets out.

Which routes this actor calls

Both routes were confirmed live against the provider before release, using deliberately invalid credentials so no real data was touched:

• POST /api/v2/auth/sign_in exchanges the username and password for a session token valid for eight hours.
• POST /api/v2/verify runs the named services against one person.

Worth knowing: the provider's own environments page writes the sign in route with a hyphen and gives the sandbox host as idu.test. Neither works. The live route is spelled with an underscore, and the sandbox host is idu-test, exactly as their own curl examples show. This actor uses the spellings that answer.

Keyword map

identity verification API, KYC API, AML screening API, sanctions screening API, PEP check API, watchlist screening, electronic identity verification, eIDV, age verification API, address verification, know your customer, anti money laundering, safe harbour verification, global identity data, onboarding compliance, fraud prevention API, national ID verification, credit bureau verification, electoral roll check, politically exposed persons.