curl -X POST "https://verification.didit.me/v3/database-validation/" \
-H "x-api-key: YOUR_API_KEY" \
-F "issuing_state=PER" \
-F "services=per_dni" \
-F "vendor_data=user-1234" \
-F "personal_number=11111111"
from didit import Didit
# Reads DIDIT_API_KEY.
client = Didit()
result = client.database_validation.validate(
issuing_state="PER",
services=["per_dni"],
personal_number="11111111",
vendor_data="user-1234",
)
print(result)
import Didit from "@didit-protocol/sdk-node";
// Reads DIDIT_API_KEY.
const didit = new Didit();
const result = await didit.databaseValidation.validate({
issuing_state: "PER",
services: ["per_dni"],
personal_number: "11111111",
vendor_data: "user-1234",
});
console.log(result);
ctx := context.Background()
// Reads DIDIT_API_KEY.
client := didit.NewClient()
result, err := client.DatabaseValidation.Validate(ctx, didit.DatabaseValidationValidateParams{
IssuingState: "PER",
Services: didit.Some([]string{"per_dni"}),
PersonalNumber: didit.String("11111111"),
VendorData: didit.String("user-1234"),
})
if err != nil {
log.Fatal(err)
}
fmt.Printf("%+v\n", result)
import java.util.List;
import me.didit.Didit;
import me.didit.types.DatabaseValidationValidateParams;
// Reads DIDIT_API_KEY.
Didit client = new Didit();
var result = client.databaseValidation().validate(DatabaseValidationValidateParams.builder()
.issuingState("PER")
.services(List.of("per_dni"))
.personalNumber("11111111")
.vendorData("user-1234")
.build());
System.out.println(result);
<?php
require 'vendor/autoload.php';
use Didit\DiditClient;
// Reads DIDIT_API_KEY.
$didit = new DiditClient();
$result = $didit->databaseValidation->validate([
'issuing_state' => 'PER',
'services' => ['per_dni'],
'personal_number' => '11111111',
'vendor_data' => 'user-1234',
]);
print_r($result->toArray());
require "didit"
# Reads DIDIT_API_KEY.
didit = Didit::Client.new
result = didit.database_validation.validate(
issuing_state: "PER",
services: ["per_dni"],
personal_number: "11111111",
vendor_data: "user-1234"
)
puts result.to_h
using System;
using System.Text.Json;
using Didit;
// Reads DIDIT_API_KEY.
using var client = new DiditClient();
var result = await client.DatabaseValidation.ValidateAsync(new DatabaseValidationValidateParams
{
IssuingState = "PER",
Services = new string[] { "per_dni" },
PersonalNumber = "11111111",
VendorData = "user-1234",
});
Console.WriteLine(JsonSerializer.Serialize(result));
{
"request_id": "req_01H…",
"status": "Approved",
"issuing_state": "PER",
"match_type": "full_match",
"validations": [
{
"outcome_code": "MATCH",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"first_name": "John",
"identification_number": "SAMPLE-ID-12345",
"last_name": "Doe",
"maternal_name": "Doe Maternal",
"paternal_name": "Doe Paternal",
"verification_letter": "G",
"verification_number": 2
},
"validation": {
"identification_number": "full_match"
}
}
]
}
{
"request_id": "req_01H…",
"status": "Declined",
"issuing_state": "PER",
"match_type": "no_match",
"validations": [
{
"outcome_code": "NO_MATCH",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"identification_number": "NO_MATCH"
},
"validation": {
"identification_number": "no_match"
}
}
]
}
{
"request_id": "req_01H…",
"status": "Declined",
"issuing_state": "PER",
"match_type": "no_match",
"validations": [
{
"outcome_code": "DOCUMENT_NOT_FOUND",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"identification_number": "NO_MATCH"
},
"validation": {
"identification_number": "no_match"
}
}
]
}
🇵🇪 Peru
Peru DNI-Verifizierung API: Echtzeit-Ausweisabfrage
Didit verifiziert DNI-Nummern in Peru per Datenbankvalidierung über die Identitätsinfrastruktur. Ab $0.20 pro Aufruf, keine Verträge, keine Mindestabnahme.
POST
/
v3
/
database-validation
/
curl -X POST "https://verification.didit.me/v3/database-validation/" \
-H "x-api-key: YOUR_API_KEY" \
-F "issuing_state=PER" \
-F "services=per_dni" \
-F "vendor_data=user-1234" \
-F "personal_number=11111111"
from didit import Didit
# Reads DIDIT_API_KEY.
client = Didit()
result = client.database_validation.validate(
issuing_state="PER",
services=["per_dni"],
personal_number="11111111",
vendor_data="user-1234",
)
print(result)
import Didit from "@didit-protocol/sdk-node";
// Reads DIDIT_API_KEY.
const didit = new Didit();
const result = await didit.databaseValidation.validate({
issuing_state: "PER",
services: ["per_dni"],
personal_number: "11111111",
vendor_data: "user-1234",
});
console.log(result);
ctx := context.Background()
// Reads DIDIT_API_KEY.
client := didit.NewClient()
result, err := client.DatabaseValidation.Validate(ctx, didit.DatabaseValidationValidateParams{
IssuingState: "PER",
Services: didit.Some([]string{"per_dni"}),
PersonalNumber: didit.String("11111111"),
VendorData: didit.String("user-1234"),
})
if err != nil {
log.Fatal(err)
}
fmt.Printf("%+v\n", result)
import java.util.List;
import me.didit.Didit;
import me.didit.types.DatabaseValidationValidateParams;
// Reads DIDIT_API_KEY.
Didit client = new Didit();
var result = client.databaseValidation().validate(DatabaseValidationValidateParams.builder()
.issuingState("PER")
.services(List.of("per_dni"))
.personalNumber("11111111")
.vendorData("user-1234")
.build());
System.out.println(result);
<?php
require 'vendor/autoload.php';
use Didit\DiditClient;
// Reads DIDIT_API_KEY.
$didit = new DiditClient();
$result = $didit->databaseValidation->validate([
'issuing_state' => 'PER',
'services' => ['per_dni'],
'personal_number' => '11111111',
'vendor_data' => 'user-1234',
]);
print_r($result->toArray());
require "didit"
# Reads DIDIT_API_KEY.
didit = Didit::Client.new
result = didit.database_validation.validate(
issuing_state: "PER",
services: ["per_dni"],
personal_number: "11111111",
vendor_data: "user-1234"
)
puts result.to_h
using System;
using System.Text.Json;
using Didit;
// Reads DIDIT_API_KEY.
using var client = new DiditClient();
var result = await client.DatabaseValidation.ValidateAsync(new DatabaseValidationValidateParams
{
IssuingState = "PER",
Services = new string[] { "per_dni" },
PersonalNumber = "11111111",
VendorData = "user-1234",
});
Console.WriteLine(JsonSerializer.Serialize(result));
{
"request_id": "req_01H…",
"status": "Approved",
"issuing_state": "PER",
"match_type": "full_match",
"validations": [
{
"outcome_code": "MATCH",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"first_name": "John",
"identification_number": "SAMPLE-ID-12345",
"last_name": "Doe",
"maternal_name": "Doe Maternal",
"paternal_name": "Doe Paternal",
"verification_letter": "G",
"verification_number": 2
},
"validation": {
"identification_number": "full_match"
}
}
]
}
{
"request_id": "req_01H…",
"status": "Declined",
"issuing_state": "PER",
"match_type": "no_match",
"validations": [
{
"outcome_code": "NO_MATCH",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"identification_number": "NO_MATCH"
},
"validation": {
"identification_number": "no_match"
}
}
]
}
{
"request_id": "req_01H…",
"status": "Declined",
"issuing_state": "PER",
"match_type": "no_match",
"validations": [
{
"outcome_code": "DOCUMENT_NOT_FOUND",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"identification_number": "NO_MATCH"
},
"validation": {
"identification_number": "no_match"
}
}
]
}
Verifiziert peruanische DNI anhand des zivilen Registers von RENIEC. Didit stellt diesen Dienst über
POST /v3/database-validation/ bereit, damit Sie die übermittelten Daten mit der maßgeblichen Quelle abgleichen und normalisierte Übereinstimmungsergebnisse erhalten. Eingabeformat: personal_number nimmt die peruanische DNI entgegen (genau 8 Ziffern).
Abdeckung
- Abdeckung: –
- Land: Peru
- Service-ID:
per_dni - Datenbereich: Identität
- Kategorie: NationalIDRegistry
Eingaben
| Feld | Pflicht | Beispiel |
|---|---|---|
personal_number | Ja | 11111111 |
first_name | Nein | John |
last_name | Nein | Doe |
vendor_data | Nein | user-1234 |
- Pflichteingaben:
personal_number - Optionale Eingaben:
first_name,last_name,vendor_data - Einwilligung: Nicht erforderlich
- Verfügbarkeit im Workflow: Im Workflow verfügbar
- Abdeckung: –
- Preis: $0.20 pro erfolgreicher Abfrage
Body-Parameter
string
Standard:"PER"
erforderlich
ISO-3166-1-Alpha-3-Ländercode für diesen Datenbankdienst.Beispiel:
PERstring
Standard:"per_dni"
erforderlich
Array mit dieser Service-ID. Durch das Festlegen des Dienstes bleibt die Anfrage auf genau diese Datenbank beschränkt.Beispiel:
per_dnistring
Standard:"11111111"
erforderlich
Länderspezifische Personenkennziffer.Beispiel:
11111111string
Zu validierender Vorname.Beispiel:
Johnstring
Zu validierender Nachname.Beispiel:
Doestring
Standard:"user-1234"
Ihre stabile Benutzerreferenz für diese Person, etwa Ihre interne Benutzer-ID. Didit verwendet sie, um eigenständige Prüfungen derselben Endbenutzerin bzw. demselben Endbenutzer zuzuordnen und unnötige Duplikatmeldungen zu reduzieren.Beispiel:
user-1234Eingaberegeln und Validierungshinweise
- Peruanische DNI (genau 8 Ziffern)
personal_numberdarf nur Ziffern enthalten; entfernen Sie Leerzeichen, Bindestriche und Satzzeichen, bevor Sie die Anfrage senden.personal_numbermuss genau 8 Zeichen lang sein.
So rufen Sie es auf
curl -X POST "https://verification.didit.me/v3/database-validation/" \
-H "x-api-key: YOUR_API_KEY" \
-F "issuing_state=PER" \
-F "services=per_dni" \
-F "vendor_data=user-1234" \
-F "personal_number=11111111"
from didit import Didit
# Reads DIDIT_API_KEY.
client = Didit()
result = client.database_validation.validate(
issuing_state="PER",
services=["per_dni"],
personal_number="11111111",
vendor_data="user-1234",
)
print(result)
import Didit from "@didit-protocol/sdk-node";
// Reads DIDIT_API_KEY.
const didit = new Didit();
const result = await didit.databaseValidation.validate({
issuing_state: "PER",
services: ["per_dni"],
personal_number: "11111111",
vendor_data: "user-1234",
});
console.log(result);
ctx := context.Background()
// Reads DIDIT_API_KEY.
client := didit.NewClient()
result, err := client.DatabaseValidation.Validate(ctx, didit.DatabaseValidationValidateParams{
IssuingState: "PER",
Services: didit.Some([]string{"per_dni"}),
PersonalNumber: didit.String("11111111"),
VendorData: didit.String("user-1234"),
})
if err != nil {
log.Fatal(err)
}
fmt.Printf("%+v\n", result)
import java.util.List;
import me.didit.Didit;
import me.didit.types.DatabaseValidationValidateParams;
// Reads DIDIT_API_KEY.
Didit client = new Didit();
var result = client.databaseValidation().validate(DatabaseValidationValidateParams.builder()
.issuingState("PER")
.services(List.of("per_dni"))
.personalNumber("11111111")
.vendorData("user-1234")
.build());
System.out.println(result);
<?php
require 'vendor/autoload.php';
use Didit\DiditClient;
// Reads DIDIT_API_KEY.
$didit = new DiditClient();
$result = $didit->databaseValidation->validate([
'issuing_state' => 'PER',
'services' => ['per_dni'],
'personal_number' => '11111111',
'vendor_data' => 'user-1234',
]);
print_r($result->toArray());
require "didit"
# Reads DIDIT_API_KEY.
didit = Didit::Client.new
result = didit.database_validation.validate(
issuing_state: "PER",
services: ["per_dni"],
personal_number: "11111111",
vendor_data: "user-1234"
)
puts result.to_h
using System;
using System.Text.Json;
using Didit;
// Reads DIDIT_API_KEY.
using var client = new DiditClient();
var result = await client.DatabaseValidation.ValidateAsync(new DatabaseValidationValidateParams
{
IssuingState = "PER",
Services = new string[] { "per_dni" },
PersonalNumber = "11111111",
VendorData = "user-1234",
});
Console.WriteLine(JsonSerializer.Serialize(result));
Jeder erfolgreiche Aufruf liefert HTTP
200 zurück. Das Feld outcome_code zeigt, was tatsächlich passiert ist. So lässt sich etwa eine echte biometrische Nichtübereinstimmung (BIOMETRIC_NO_MATCH) von einem Selfie unterscheiden, das nicht gelesen werden konnte (BIOMETRIC_IMAGE_UNUSABLE). Der angezeigte status ist der Standardstatus des Features; Ihre konfigurierten Aktionen für Partial Match / No Match können ihn überschreiben.MATCH: Das Register hat die Identität bestätigt, und alle geprüften Felder stimmen überein.{
"request_id": "req_01H…",
"status": "Approved",
"issuing_state": "PER",
"match_type": "full_match",
"validations": [
{
"outcome_code": "MATCH",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"first_name": "John",
"identification_number": "SAMPLE-ID-12345",
"last_name": "Doe",
"maternal_name": "Doe Maternal",
"paternal_name": "Doe Paternal",
"verification_letter": "G",
"verification_number": 2
},
"validation": {
"identification_number": "full_match"
}
}
]
}
NO_MATCH: Das Register hat für die übermittelten Daten keine Übereinstimmung geliefert.{
"request_id": "req_01H…",
"status": "Declined",
"issuing_state": "PER",
"match_type": "no_match",
"validations": [
{
"outcome_code": "NO_MATCH",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"identification_number": "NO_MATCH"
},
"validation": {
"identification_number": "no_match"
}
}
]
}
DOCUMENT_NOT_FOUND: Die übermittelte Dokumentnummer entspricht keinem Datensatz im Register.{
"request_id": "req_01H…",
"status": "Declined",
"issuing_state": "PER",
"match_type": "no_match",
"validations": [
{
"outcome_code": "DOCUMENT_NOT_FOUND",
"service_id": "per_dni",
"service_name": "Peru - DNI verification",
"source_data": {
"identification_number": "NO_MATCH"
},
"validation": {
"identification_number": "no_match"
}
}
]
}
Zurückgegebene Daten
Welche genauen Felder insource_data erscheinen, hängt davon ab, was das Register zurückgibt. Das generierte Beispiel für per_dni dokumentiert derzeit folgende normalisierte Struktur:
first_nameidentification_numberlast_namematernal_namepaternal_nameverification_letterverification_number
Preise & SLAs
Peru - DNI-Verifizierungsabfragen werden nur abgerechnet, wenn Didit von der Validierungsquelle ein eindeutiges Ergebnis erhält.- Preis pro Abfrage: $0.20 USD.
- Abrechnung: pro erfolgreicher Abfrage. Es wird nichts berechnet, wenn das Register nicht erreichbar ist, wenn Pflichtfelder fehlen oder wenn die Anfrage abgelehnt wird, bevor sie die Quelle erreicht.
- Latenz: typischer p95 < 2 s.
- Verfügbarkeit: 99.9% pro Quartal auf Seiten von Didit; die Verfügbarkeit der nachgelagerten Quelle variiert je nach Land und Datensatz.
Weiterlesen
Zuletzt geändert am 7. November 2026