France Phone

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=FRA" \
  -F "services=fra_phone" \
  -F "vendor_data=user-1234" \
  -F "first_name=John" \
  -F "last_name=Doe" \
  -F "phone=+15550101000"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "FRA",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "fra_phone",
      "service_name": "France Phone",
      "source_data": {
        "address": "123 Sample Street",
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "last_name": "Doe"
      },
      "validation": {
        "full_name": "full_match"
      }
    }
  ]
}

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "FRA",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "fra_phone",
      "service_name": "France Phone",
      "source_data": {
        "full_name": "NO_MATCH"
      },
      "validation": {
        "full_name": "no_match"
      }
    }
  ]
}

POST

database-validation

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=FRA" \
  -F "services=fra_phone" \
  -F "vendor_data=user-1234" \
  -F "first_name=John" \
  -F "last_name=Doe" \
  -F "phone=+15550101000"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "FRA",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "fra_phone",
      "service_name": "France Phone",
      "source_data": {
        "address": "123 Sample Street",
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "last_name": "Doe"
      },
      "validation": {
        "full_name": "full_match"
      }
    }
  ]
}

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "FRA",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "fra_phone",
      "service_name": "France Phone",
      "source_data": {
        "full_name": "NO_MATCH"
      },
      "validation": {
        "full_name": "no_match"
      }
    }
  ]
}

Verifies input data to mobile network operators phone data. Didit exposes this service through POST /v3/database-validation/ so you can verify the submitted data against the authoritative source and receive normalized match results.

Coverage

Coverage: ~ 90%
Country: France
Service ID: fra_phone
Data domain: Telecom
Category: Telecom

Inputs

Field	Required	Example
`first_name`	Yes	`John`
`last_name`	Yes	`Doe`
`phone`	Yes	`+15550101000`
`date_of_birth`	No	`1990-01-01`
`address.street_1`	No	`123 Sample Street`
`address.street_2`	No	`Unit 4`
`address.city`	No	`Sample City`
`address.region`	No	`Sample State`
`address.postal_code`	No	`10001`
`vendor_data`	No	`user-1234`

Required inputs: first_name, last_name, phone
Optional inputs: date_of_birth, address.street_1, address.street_2, address.city, address.region, address.postal_code, vendor_data
Consent: Not required
Workflow availability: Standalone API only
Coverage: ~ 90%
Price: $0.67 per successful query

Body parameters

string

default:"FRA"

required

ISO 3166-1 alpha-3 country code for this database service.Example: FRA

string

default:"fra_phone"

required

Array containing this service ID. Pinning the service keeps the request scoped to this exact database.Example: fra_phone

string

default:"John"

required

Given name to validate.Example: John

string

default:"Doe"

required

Family name to validate.Example: Doe

string

default:"+15550101000"

required

Phone number in international format.Example: +15550101000

string

default:"1990-01-01"

Date of birth in YYYY-MM-DD format.Example: 1990-01-01

object

Structured residential address object. Use street_1, street_2, city, region, postal_code, and country. A complete legacy address string is still accepted but not recommended.Example:

{"street_1":"123 Sample Street","street_2":"Unit 4","city":"Sample City","region":"Sample State","postal_code":"10001","country":"US"}

string

default:"user-1234"

Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise.Example: user-1234

Input rules & validation notes

address is optional for this service. You can send one complete address string and Didit will split it into structured address elements when possible, or you can send the structured fields explicitly.
For address services, send structured address fields instead of a single address string when possible.
address.street_1 is the street address, including street number and street type.
address.street_2 is apartment, unit, building, floor, or extra address line. Send it only when you have it.
address.city is city, suburb, district, locality, or neighborhood.
address.region is state, province, region, or town.
address.postal_code is postcode or postal code.
Address-based database services require at least street address and postal code; requests rejected before source lookup are not charged.

How to call it

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=FRA" \
  -F "services=fra_phone" \
  -F "vendor_data=user-1234" \
  -F "first_name=John" \
  -F "last_name=Doe" \
  -F "phone=+15550101000"

Every successful call returns HTTP 200. The outcome_code field tells you what actually happened — distinguishing, for example, a real biometric mismatch (BIOMETRIC_NO_MATCH) from a selfie that could not be read (BIOMETRIC_IMAGE_UNUSABLE). The status shown is the default feature status; your configured Partial Match / No Match actions can override it.

MATCH — The registry confirmed the identity and every checked field matched.

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "FRA",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "fra_phone",
      "service_name": "France Phone",
      "source_data": {
        "address": "123 Sample Street",
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "last_name": "Doe"
      },
      "validation": {
        "full_name": "full_match"
      }
    }
  ]
}

NO_MATCH — The registry returned no match for the submitted data.

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "FRA",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "fra_phone",
      "service_name": "France Phone",
      "source_data": {
        "full_name": "NO_MATCH"
      },
      "validation": {
        "full_name": "no_match"
      }
    }
  ]
}

Returned data

The exact fields surfaced in source_data depend on what the registry returns. The generated example for fra_phone currently documents this normalized shape:

address
date_of_birth
first_name
last_name

Pricing & SLAs

France Phone queries are billed only when Didit receives a conclusive result from the validation source.

Per-call price: $0.67 USD.
Billing: per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source.
Latency: typical p95 < 2 s.
Availability: 99.9% per quarter on Didit’s side; downstream source availability varies by country and dataset.

Continue reading

⌘I

Overview

User and Business Verifications

Lists

Workflows

Questionnaires

Users

Businesses

Cases

Case Blueprints

Report Templates

Regulatory Reports

Transactions

Travel Rule

Session Operations

Customization

Webhook

Billing

Management API Overview

Auth API (Programmatic)

Identity & Documents

Database Validation

Biometrics & Face

Compliance & Risk

Email Verification

Phone Verification

Coverage

Inputs

Body parameters

Input rules & validation notes

How to call it

Returned data

Pricing & SLAs

Continue reading

​Coverage

​Inputs

​Body parameters

​Input rules & validation notes

​How to call it

​Returned data

​Pricing & SLAs

​Continue reading

Coverage

Inputs

Body parameters

Input rules & validation notes

How to call it

Returned data

Pricing & SLAs

Continue reading