Guatemala CUI Verification API: Validate the DPI with Date of Birth

Updated November 2026

This guide shows how to verify a CUI in Guatemala 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 CUI in Guatemala

Guatemala’s Documento Personal de Identificación (DPI) is issued by RENAP, the Registro Nacional de las Personas. Its key number is the Código Único de Identificación (CUI), a 13-digit code whose last digits identify the department and municipality of registration.

Verifik’s endpoint uses the document type CUI plus the date of birth and returns the holder’s name split into first names, last names and name parts.

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

How to call the Guatemala CUI API

Endpoint: GET https://api.verifik.co/v2/gt/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/gt/cedula?documentType=CUI&documentNumber=1234567890101&dateOfBirth=12/03/1984' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <token>'

200 response from the docs (personal data masked):

{
  "data": {
    "arrayName": [
      "E****",
      "R******",
      "R******",
      "M******"
    ],
    "documentNumber": "22*********03",
    "documentType": "CUI",
    "firstName": "E**** R******",
    "fullName": "E**** R****** R****** M******",
    "lastName": "R****** M******"
  },
  "signature": {
    "dateTime": "January 16, 2024 3:44 PM",
    "message": "Certified by Verifik.co"
  },
  "id": "GT001"
}

A successful call returns HTTP 200 with a data object containing: arrayName, documentNumber, documentType, firstName, fullName, lastName. 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/gt/cedula

• 401 UNAUTHORIZED (“Authentication required”): the token is missing or invalid; check the Authorization header.
• 409 MissingParameter (“missing documentType missing documentNumber 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

• All three parameters are required. Missing any of them returns 409 MissingParameter listing what is absent.
• Send the date as DD/MM/YYYY, for example 12/03/1984.
• Remove the spaces users copy from the DPI card (it is printed in groups of 4-5-4 digits).
• Use arrayName to compare names that include several given names or a married surname.

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

• El Salvador DUI verification API
• Honduras 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.