Sweden National ID

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=SWE" \
  -F "services=swe_national_id" \
  -F "vendor_data=user-1234" \
  -F "first_name=John" \
  -F "last_name=Doe" \
  -F "date_of_birth=1990-01-01" \
  -F "national_id=11111111"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "SWE",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe",
        "name_match_score": "1.000",
        "verifications": {
          "date_of_birth": true,
          "full_name": true,
          "identification_number": true
        }
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "full_match",
        "identification_number": "full_match"
      }
    }
  ]
}

{
  "request_id": "req_01H…",
  "status": "In Review",
  "issuing_state": "SWE",
  "match_type": "partial_match",
  "validations": [
    {
      "outcome_code": "PARTIAL_MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe",
        "name_match_score": "1.000",
        "verifications": {
          "date_of_birth": true,
          "full_name": false,
          "identification_number": true
        }
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "no_match",
        "identification_number": "full_match"
      }
    }
  ]
}

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "SWE",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "NO_MATCH",
        "full_name": "NO_MATCH",
        "identification_number": "NO_MATCH"
      },
      "validation": {
        "date_of_birth": "no_match",
        "full_name": "no_match",
        "identification_number": "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=SWE" \
  -F "services=swe_national_id" \
  -F "vendor_data=user-1234" \
  -F "first_name=John" \
  -F "last_name=Doe" \
  -F "date_of_birth=1990-01-01" \
  -F "national_id=11111111"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "SWE",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe",
        "name_match_score": "1.000",
        "verifications": {
          "date_of_birth": true,
          "full_name": true,
          "identification_number": true
        }
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "full_match",
        "identification_number": "full_match"
      }
    }
  ]
}

{
  "request_id": "req_01H…",
  "status": "In Review",
  "issuing_state": "SWE",
  "match_type": "partial_match",
  "validations": [
    {
      "outcome_code": "PARTIAL_MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe",
        "name_match_score": "1.000",
        "verifications": {
          "date_of_birth": true,
          "full_name": false,
          "identification_number": true
        }
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "no_match",
        "identification_number": "full_match"
      }
    }
  ]
}

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "SWE",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "NO_MATCH",
        "full_name": "NO_MATCH",
        "identification_number": "NO_MATCH"
      },
      "validation": {
        "date_of_birth": "no_match",
        "full_name": "no_match",
        "identification_number": "no_match"
      }
    }
  ]
}

Verifies input data against the Swedish Police Authority service. 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: ~ 100%
Country: Sweden
Service ID: swe_national_id
Data domain: Identity
Category: NationalIDRegistry

Inputs

Field	Required	Example
`first_name`	Yes	`John`
`last_name`	Yes	`Doe`
`date_of_birth`	Yes	`1990-01-01`
`national_id`	Yes	`11111111`
`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, date_of_birth, national_id
Optional inputs: address.street_1, address.street_2, address.city, address.region, address.postal_code, vendor_data
Consent: Not required
Workflow availability: Available in workflow
Coverage: ~ 100%
Price: $0.35 per successful query

Body parameters

string

default:"SWE"

required

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

string

default:"swe_national_id"

required

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

string

default:"John"

required

Given name to validate.Example: John

string

default:"Doe"

required

Family name to validate.Example: Doe

string

default:"1990-01-01"

required

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

string

default:"11111111"

required

National identity number for this service.Example: 11111111

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.
national_id must contain digits only; remove spaces, hyphens, and punctuation before sending the request.
national_id must match (\d{10}|\d{12}).
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=SWE" \
  -F "services=swe_national_id" \
  -F "vendor_data=user-1234" \
  -F "first_name=John" \
  -F "last_name=Doe" \
  -F "date_of_birth=1990-01-01" \
  -F "national_id=11111111"

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": "SWE",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe",
        "name_match_score": "1.000",
        "verifications": {
          "date_of_birth": true,
          "full_name": true,
          "identification_number": true
        }
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "full_match",
        "identification_number": "full_match"
      }
    }
  ]
}

PARTIAL_MATCH — The identification number was found but one or more personal fields (usually name or date of birth) did not fully match.

{
  "request_id": "req_01H…",
  "status": "In Review",
  "issuing_state": "SWE",
  "match_type": "partial_match",
  "validations": [
    {
      "outcome_code": "PARTIAL_MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "first_name": "John",
        "full_name": "John Doe",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe",
        "name_match_score": "1.000",
        "verifications": {
          "date_of_birth": true,
          "full_name": false,
          "identification_number": true
        }
      },
      "validation": {
        "date_of_birth": "full_match",
        "full_name": "no_match",
        "identification_number": "full_match"
      }
    }
  ]
}

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

{
  "request_id": "req_01H…",
  "status": "Declined",
  "issuing_state": "SWE",
  "match_type": "no_match",
  "validations": [
    {
      "outcome_code": "NO_MATCH",
      "service_id": "swe_national_id",
      "service_name": "Sweden National ID",
      "source_data": {
        "date_of_birth": "NO_MATCH",
        "full_name": "NO_MATCH",
        "identification_number": "NO_MATCH"
      },
      "validation": {
        "date_of_birth": "no_match",
        "full_name": "no_match",
        "identification_number": "no_match"
      }
    }
  ]
}

Returned data

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

date_of_birth
first_name
full_name
identification_number
last_name
name_match_score

Pricing & SLAs

Sweden National ID queries are billed only when Didit receives a conclusive result from the validation source.

Per-call price: $0.35 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