Automate CIC Verification for Paraguay

Paraguay Cédula Verification API (CIC): Name Lookup by Document Number

Table of Contents
Share this article

Updated November 2026

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

Paraguay’s Cédula de Identidad Civil (CIC) is issued by the Departamento de Identificaciones of the Policía Nacional. It is a numeric document of up to seven or eight digits and it is the identifier used for banking, telecom contracts and the tax RUC of individuals.

Verifik’s endpoint needs only the document number and returns the registered first name, last name and full name.

To follow this guide with your own integration, open a Verifik account and generate your access token.

How to call the Paraguay CIC API

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

ParameterRequiredDescription
documentNumberYesCIC document number.

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

curl --location --request GET 'https://api.verifik.co/v2/py/cic?documentNumber=1234567' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer <token>'

200 response from the docs (personal data masked):

{
  "data": {
    "documentNumber": "12***67",
    "firstName": "F*******",
    "lastName": "S****",
    "fullName": "F******* S****"
  },
  "signature": {
    "message": "Certified by Verifik.co",
    "dateTime": "January 16, 2024 3:44 PM"
  },
  "id": "PY001"
}

A successful call returns HTTP 200 with a data object containing: 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/py/cic

  • 400 INVALID_DOCUMENT (“Invalid document number”): the document number failed validation; ask the user to re-check it before retrying.

Integration tips

  • Send the CIC without dots or separators (users often type 1.234.567).
  • There is no documentType parameter for this endpoint; only documentNumber.
  • A 400 INVALID_DOCUMENT means the number failed validation.
  • Because the check needs only a number, add a second factor (selfie or document photo) for high-risk flows.

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

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.

Miguel Treviño - Co-founder and CTO, Verifik

Frequently Asked Questions (FAQs)

➖

Which parameters does the Paraguay CIC endpoint need?

Only documentNumber, the CIC without separators.

➕

Which endpoint verifies a CIC in Paraguay?

GET https://api.verifik.co/v2/py/cic, with the parameter documentNumber and your Bearer token.

➕

What errors can the Paraguay CIC endpoint return?

The documentation lists HTTP 400. In short, 400 usually means a missing or invalid parameter.

➕

How is the Paraguay CIC check priced?

Each successful request consumes credits from your Verifik plan. See the smartCHECK pricing page for current plans.

Explore more articles