Uruguay Cédula Verification API (CCUY): Name and Date of Birth Match

Updated November 2026

This guide shows how to verify a cédula in Uruguay with Verifik’s API: the endpoint, its parameters, a request you can paste into a terminal, the documented response and errors, and what to watch for when you put it in production. Everything below comes from the official endpoint documentation.

About the cédula in Uruguay

The Uruguayan cédula de identidad is issued by the Dirección Nacional de Identificación Civil (DNIC), part of the Ministry of the Interior. It is the document Uruguayans use for banking, telecom contracts and almost every formal transaction, so it is the natural anchor for KYC in the country.

Verifik’s endpoint uses the document type CCUY and requires the holder’s date of birth. The record is only returned when both the number and the birth date match.

Want to try it? Create your Verifik account and make your first call today.

How to call the Uruguay cédula API

Endpoint: GET https://api.verifik.co/v2/uy/cedula. Send your token in the Authorization: Bearer header. Parameters, as documented:

Request example with placeholder values (replace them with your user’s data):

curl --location --request GET 'https://api.verifik.co/v2/uy/cedula?documentType=CCUY&documentNumber=12345678&dateOfBirth=15/03/1990' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <token>'

200 response from the docs (personal data masked):

{
  "data": {
    "documentType": "CCUY",
    "documentNumber": "12*****89",
    "firstName": "A**",
    "lastName": "G*****",
    "fullName": "A** G*****"
  },
  "signature": {
    "message": "Certified by Verifik.co",
    "dateTime": "January 16, 2024 3:44 PM"
  },
  "id": "UY001"
}

A successful call returns HTTP 200 with a data object containing: documentType, documentNumber, firstName, lastName, fullName. Every response also carries a signature (timestamp and “Certified by Verifik.co”) and a unique id you can store as evidence of the check.

Documented errors for /v2/uy/cedula

• 401 UNAUTHORIZED (“Authentication required”): the token is missing or invalid; check the Authorization header.
• 403 FORBIDDEN (“Access forbidden”): the token is valid but not allowed to use this endpoint; check your plan or permissions.
• 404 NotFound (“Record not found”): no record was found; do not treat it as a match and route the case to review or ask for another document.
• 409 MissingParameter (“missing dateOfBirth”): a required parameter is missing or has an invalid value; fix the request instead of retrying it as is.
• 500 InternalServerError (“Server error”): a server or source error; retry with backoff and log the request id.

Integration tips

• Collect the date of birth in the same step as the cédula number; it is a required parameter (409 missing dateOfBirth if absent).
• Format the date as DD/MM/YYYY before sending it, regardless of how your form captures it.
• Compare the returned fullName with the name typed by the user using a tolerant match (accents, double surnames).
• Treat 404 as “no match” and ask the user to review the number and birth date instead of retrying automatically.

Personal data and terms of use

Identity lookups process personal data. Use the API only for a lawful purpose you can document, such as onboarding, fraud prevention or contract checks, collect consent where the local law requires it, and keep only the fields you need. Usage is governed by the smartCHECK terms and conditions.

Pricing

Each successful request consumes credits from your Verifik plan. Current plans and per-endpoint costs are on the smartCHECK pricing page.

Related guides and documentation

• Paraguay CIC verification API
• Argentina DNI verification API
• Endpoint documentation (English)
• Documentation in Spanish

Start testing

Create a Verifik account to get your API token, or book a meeting if you want to review coverage and volumes with the team.