Venezuela Cédula Verification API

Onboarding users in Venezuela means confirming they are who they claim to be. Verifies Venezuelan Cédula against the SAIME civil registry. A document or a typed-in detail only proves the data exists — not that it is genuine or belongs to the person in front of you. Venezuela Cédula Verification closes that gap by checking the data against the country's official government identity registry. This guide explains what the check does, the exact technical details, and how to integrate it in minutes.

Key takeaways:

• What it checks — Venezuela Cédula Verification validates national ID against the country's official government identity registry.
• What you get back — a normalized match_type plus field-level results you can route straight into approve / review / reject logic.
• Why it matters — A document can be forged; a registry record cannot. Validating the ID against the authoritative government source confirms the holder is real and correctly identified.
• How to use it — one POST to Didit's database-validation endpoint, or a no-code workflow module. $0.20 per conclusive query, results in seconds.

What Venezuela Cédula Verification validates

Verifies Venezuelan Cédula against the SAIME civil registry. Didit exposes it through a single endpoint so you can verify the submitted data against the country's official government identity registry and receive a structured, normalized result — not a raw registry dump you have to parse yourself.

A conclusive response returns the matched source_data and a per-field validation block, so your risk engine gets a clear, machine-readable verdict.

Why it matters

A document can be forged; a registry record cannot. Validating the ID against the authoritative government source confirms the holder is real and correctly identified.

For regulated businesses in Venezuela — fintechs, crypto platforms, lenders, marketplaces, and gaming operators — checking against an authoritative source produces a defensible, auditable record that identity was confirmed at the source, not merely captured from a form or a photo.

Technical details

Didit exposes this service through the unified database-validation endpoint. It is a single POST — no SDK required.

Endpoint

POST /v3/database-validation/

Request parameters

Parameter	Type	Required	Description
issuing_state	string	Yes	ISO 3166-1 alpha-3 country code. Use VEN.
services	string	Yes	Service identifier. Use ven_cedula.
document_number	string	Yes	Document number.
first_name	string	No	First name (optional cross-check).
last_name	string	No	Last name (optional cross-check).

Example request

curl -X POST "https://verification.didit.me/v3/database-validation/" \
  -H "x-api-key: YOUR_API_KEY" \
  -F "issuing_state=VEN" \
  -F "services=ven_cedula" \
  -F "document_number=1111111"

Example response (conclusive match)

{
  "request_id": "req_01H...",
  "status": "Approved",
  "issuing_state": "VEN",
  "match_type": "full_match",
  "validations": [
    {
      "outcome_code": "MATCH",
      "service_id": "ven_cedula",
      "service_name": "Venezuela - Cédula verification",
      "source_data": {
        "date_of_birth": "1990-01-01",
        "document_type": "sample_value",
        "first_name": "John",
        "full_name": "John Doe",
        "gender": "M",
        "identification_number": "SAMPLE-ID-12345",
        "last_name": "Doe"
      },
      "validation": {
        "full_name": "full_match",
        "identification_number": "full_match"
      }
    }
  ]
}

Performance and billing

• Latency: typically a couple of seconds.
• Cost: $0.20 per conclusive query. You are billed only on conclusive results — no charge for source downtime, missing fields, or pre-source rejections.
• Reliability: runs on Didit's infrastructure with a 99.9% quarterly uptime target.

Use cases

• Fintech & neobanks — confirm a real, verifiable account holder before opening a wallet or extending credit in Venezuela.
• Crypto & Web3 — meet VASP onboarding requirements with authoritative-source identity proof.
• Lending — reduce synthetic-identity and first-party fraud with source-verified data.
• Marketplaces & gig platforms — verify users against authoritative data, not just a self-reported form.
• iGaming — satisfy identity and eligibility checks for Venezuela players with an auditable trail.

How to integrate with Didit

You can run Venezuela Cédula Verification two ways:

1. No-code workflow. In the Didit Business Console, open the Workflow Builder, add the Database Validation module, select Venezuela → Venezuela Cédula Verification, and activate it. Matching users are routed automatically — no engineering required.
2. Direct API. Call the /v3/database-validation/ endpoint shown above with services=ven_cedula. Read match_type and the per-field validation block to drive your approve / review / reject logic.

Every Didit account includes 500 free verifications per month, so you can test the full flow end-to-end before you pay for a single query.

Frequently asked questions

What does the Venezuela Cédula Verification check confirm?

It validates the submitted data against the country's official government identity registry and returns a normalized match result, so you learn whether the national ID exists at the authoritative source and which fields matched.

What happens if the source is temporarily unavailable?

You are not charged. Billing applies only to conclusive results — source downtime, missing fields, and pre-source rejections are free.

How fast is the check?

Database validation typically returns in a couple of seconds, so it fits inside a real-time onboarding flow.

Do I need an SDK?

No. The check is a single HTTPS POST to one endpoint. You can also wire it into a no-code workflow in the Business Console.

Ready to get started?

Validate your first Venezuela national ID today.

• Read the API reference: Venezuela Cédula Verification
• See all database validations: Database Validation pricing & coverage
• Start building: Create a free Didit account — 500 verifications a month, free.