Colombia — National ID with extra data (CC)

See the product page: Colombia KYC API.

Verifik returns extended Colombian national ID data for Cédula de Ciudadanía (CC) holders by matching document number and issue date against official sources. Typical fields include full name, expedition place and date, date of birth, gender, and living status when returned by the source.

This dataset is more sensitive than the basic cédula lookup; use it only where your policy and law allow.

If you need the same style of enriched record but without supplying the issue date up front, use National ID premium (CC) (GET/POST /v2/co/cedula/premium — expedition date resolved automatically; CC only, premium pricing).

What this API returns

• Identity fields (name parts, document type/number)
• Expedition metadata (date, place) aligned to the query
• Extended personal fields such as date of birth, gender, and isAlive when available
• Signed responses; repeat lookups may be cached

API reference

Endpoint

GET https://api.verifik.co/v2/co/cedula/extra

The same integration is available as POST with a JSON body containing the same fields. GET uses query parameters as shown below.

Headers

Name	Value
Accept	application/json
Authorization	Bearer <token>

Parameters

name	type	required	description
documentType	string	yes	Must be CC.
documentNumber	string	yes	CC number without spaces or punctuation.
date	string	yes	Issue date of the document in DD/MM/YYYY.

Request

JavaScript

import axios from "axios";

const { data } = await axios.get("https://api.verifik.co/v2/co/cedula/extra", {
	params: {
		documentType: "CC",
		documentNumber: "123456789",
		date: "10/10/2020",
	},
	headers: {
		Accept: "application/json",
		Authorization: `Bearer ${process.env.VERIFIK_TOKEN}`,
	},
});
console.log(data);

Python

import os, requests

url = "https://api.verifik.co/v2/co/cedula/extra"
headers = {"Accept": "application/json", "Authorization": f"Bearer {os.getenv('VERIFIK_TOKEN')}"}
params = {"documentType": "CC", "documentNumber": "123456789", "date": "10/10/2020"}
r = requests.get(url, headers=headers, params=params)
print(r.json())

Response

200

{
	"data": {
		"documentType": "CC",
		"documentNumber": "123456789",
		"fullName": "MATEO VERIFIK",
		"firstName": "MATEO",
		"lastName": "VERIFIK",
		"arrayName": ["MATEO", "VERIFIK"],
		"expeditionDate": "2022-05-10T00:00:00.000Z",
		"expeditionPlace": {
			"municipio": "BOGOTA D.C.",
			"departamento": "BOGOTA"
		},
		"dateOfBirth": "1999-05-07T00:00:00.000Z",
		"gender": "HOMBRE",
		"isAlive": true
	},
	"signature": {
		"dateTime": "August 23, 2022 11:42 AM",
		"message": "Certified by Verifik.co"
	}
}

404 (Not Found)

{
	"code": "NotFound",
	"message": "Record not found."
}

Returned when the official government registry (RNEC) confirms that the document does not exist or the issue date does not correspond to the document number (verified via 2 consecutive confirmed checks).

409 (Out of Service / Missing Param)

{
	"code": "Conflict",
	"message": "Endpoint_out_of_service"
}

Returned when upstream government registries (RNEC / SIMO) are experiencing temporary degradation, maintenance, or connection timeouts. No credits are deducted. Clients should retry shortly or route to manual review rather than rejecting the customer.

Also returned if the date parameter is missing or format is invalid:

{
	"code": "MissingParameter",
	"message": "date format required: DD/MM/YYYY\n"
}

Features

• CC-only validation at the API layer
• Issue date (date) must match DD/MM/YYYY

Use cases

• High-assurance KYC with demographic confirmation
• Fraud and impersonation risk reduction when issue date is known

Notes

• date is the document issue date, not the date of birth.
• 404 vs 409 semantics: The 404 status is strictly reserved for confirmed registry non-existence or date mismatch (verified by 2 consecutive checks). Upstream government registry downtime or timeouts return 409 Endpoint_out_of_service without credit deduction.
• Wrong DD/MM/YYYY format returns 409 MissingParameter.
• GET and POST share the same handler; use POST if you prefer a JSON body.
• Returned fields may include special-category personal data; comply with Colombian privacy rules and your contracts.