Skip to main content
POST
/
v3
/
database-validation
curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=DOM" \
  -F "personal_number=00100000001" \
  -F "services=dom_cedula"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "DOM",
  "match_type": "full_match",
  "validations": [
    {
      "service_id": "dom_cedula",
      "outcome_code": "MATCH",
      "validation": {
        "personal_number": "full_match"
      },
      "source_data": {
        "personal_number": "00100000001"
      }
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.didit.me/llms.txt

Use this file to discover all available pages before exploring further.

Dominican Republic Database Validation queries the Junta Central Electoral (JCE) directly — the constitutional body that operates the Dominican civil and electoral registry. Direct integration means low latency and the lowest per-call price in our catalog ($0.05). Each lookup returns the holder’s full name, date of birth, gender and registry status.

​
What you need

FieldRequiredNotes
personal_numberYesCédula de Identidad y Electoral
Format rule: Cédula is exactly 11 digits, no separators. Regulatory context: Dominican KYC programs typically combine JCE (Junta Central Electoral) Cédula verification with SIB supervision (Superintendencia de Bancos) and BCRD (Banco Central de la República Dominicana) requirements. The JCE maintains both the Registro Civil and the Padrón Electoral and is the only authoritative source for Cédula data.

​
Available service

  • dom_cedula — verification against Junta Central Electoral (JCE). $0.05 per call. Selected automatically when services is omitted in the request.

​
How to call it

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=DOM" \
  -F "personal_number=00100000001" \
  -F "services=dom_cedula"

{
  "request_id": "req_01H…",
  "status": "Approved",
  "issuing_state": "DOM",
  "match_type": "full_match",
  "validations": [
    {
      "service_id": "dom_cedula",
      "outcome_code": "MATCH",
      "validation": {
        "personal_number": "full_match"
      },
      "source_data": {
        "personal_number": "00100000001"
      }
    }
  ]
}

​
Returned data

A successful match returns the registry’s record for the holder. Available fields for Junta Central Electoral:
  • name
  • lastname
  • date_of_birth
  • gender
  • place_of_birth
  • registry_status
The exact fields surfaced in source_data depend on what the registry returns — fields that are absent from the registry record (e.g. an unset expiration_date) are simply omitted.

​
Common use cases

  • Onboarding fintechs under the Superintendencia de Bancos rules.
  • Cross-border remittance KYC.
  • Lottery / online gaming operators (compliance with Dirección General de Casinos).

​
Pricing & SLAs

Dominican Cédula lookups against the Junta Central Electoral are the cheapest in our LATAM catalog at $0.05/check — the registry returns the legal name, gender and date of birth on every successful query.
  • Per-call price: $0.05 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 registry.
  • Latency: typical p95 < 1.5 s.
  • Availability: 99.9% per quarter.

​
Other live database services

​
Continue reading

Dominican Superintendencia de Bancos onboarding under SIB rules often combines Junta Central Electoral with Face Match.

Authorizations

​
x-api-key
string
header
required

Body

multipart/form-data
​
issuing_state
enum<string>
required

The ISO 3166-1 alpha-3 country code of the issuing state. Determines which validation sources are used.

Available options:
ARG,
BOL,
BRA,
CHL,
COL,
CRI,
DOM,
ECU,
ESP,
GTM,
HND,
MEX,
PAN,
PER,
PRY,
SLV,
URY,
VEN
​
identification_number
string
required

Universal identification number field. Automatically maps to the correct country-specific field: ARG→document_number (DNI), BOL→document_number (CI), BRA→tax_number (CPF, 11 digits), CHL→personal_number (RUT), COL→personal_number (Cédula), CRI→personal_number (Cédula), DOM→personal_number (Cédula, 11 digits), ECU→personal_number (Cédula, 10 digits), ESP→personal_number (DNI/NIE), GTM→document_number (DPI), HND→document_number (DNI), MEX→personal_number (CURP, 18 chars), PAN→personal_number (Cédula), PER→personal_number (DNI, 8 digits), PRY→document_number (CI), SLV→document_number (DUI), URY→personal_number (CI), VEN→document_number (Cédula).

​
services
string[]

Optional list of service_ids to run for this country (e.g. ['bra_cpf']). If omitted, every service configured for the issuing_state is queried in waterfall order. Each id must be a service that exists for the given country — see the catalog endpoint /v1/organization/database-validation-countries/. When provided, the response contains the extended services_used, providers_used, and match_score fields.

​
first_name
string

The individual's first name. Might be required for some countries and matching types.

​
last_name
string

The individual's last name. Might be required for some countries and matching types.

​
date_of_birth
string

The individual's date of birth in YYYY-m-d format. Might be required for some countries and matching types. Example: 1990-01-01.

​
document_type
enum<string>

The type of document being validated. P = Passport, DL = Driver License, ID = National ID, RP = Residence Permit. Optional field that may help with validation in some countries.

Available options:
P,
DL,
ID,
RP
​
expiration_date
string<date>

The document's expiration date in YYYY-MM-DD format. Required for ESP (Spain) database validation. Example: 2030-01-15.

​
nationality
string

The individual's nationality, expressed as an ISO 3166-1 alpha-3 country code. Might be required for some countries and matching types.

​
address
string

The individual's residential address. Used in specific jurisdictions where address validation is supported. Might be required for some countries and matching types.

​
selfie
file

A selfie image of the individual (JPEG, PNG, or WebP). Required for ARG (Argentina) where biometric face-match is performed via RENAPER, and for PAN (Panama) where biometric validation is performed via SIB (Servicio de Identificación Biométrica). For ARG, the gender field (M/F/X) is also required.

​
gender
enum<string>

The individual's gender. Required for ARG (Argentina) biometric validation via RENAPER. M = Male, F = Female, X = Non-binary. When used within a verification session flow, gender is automatically extracted from the ID document or inferred from face analysis / given name.

Available options:
M,
F,
X
​
save_api_request
boolean
default:true

Whether to save this API request. If true, then it will appear on the Manual Checks section in the Business Console.

​
vendor_data
string

A unique identifier for the vendor or user, such as a UUID or email. This field enables proper session tracking and user data aggregation across multiple verification sessions.

Response