Skip to main content

Colombia — National ID premium lookup (CC)

Purpose: confirm a Colombian Cédula de Ciudadanía (CC) against official sources and return a structured identity record suitable for KYC and compliance workflows—not a binary pass/fail on the number alone. The response reflects how the name is recorded, date of birth, place and date of issue, and—where provided by sources—gender and alive status, with a signed certification block in the response. Submit only the document number; the issue date is resolved server-side (no documentType or issue date in the request). Record depth matches cédula extra. Credit consumption is higher than the basic cédula endpoint because of additional resolution steps.

API reference​

Endpoint​

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

Response: Returns data (identity attributes returned for the submitted number), signature (certification metadata for the payload), and id (request identifier). HTTP 404 indicates that a complete identity record could not be assembled for the supplied number under this workflow. HTTP 409 indicates that the request failed validation (for example, documentNumber length) before upstream resolution. Per-request credit cost exceeds the basic /v2/co/cedula route because of the chained resolution.

Headers​

NameValue
Acceptapplication/json
AuthorizationBearer <token>

Parameters​

NameTypeRequiredDescription
documentNumberstringYesCC number, digits only after normalization (non-digits stripped). 5–10 characters (API validation).

Notes​

  • CC only — there is no documentType on this route; the flow always treats the number as CC (see controller).
  • Prefer digits only in documentNumber (spaces and separators are stripped server-side).
  • For PPT, CE, or other types, use the appropriate dedicated endpoints—not this one.

Request​

import axios from "axios";

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

Response​

Example shape (illustrative placeholders, not real individuals):

{
	"data": {
		"arrayName": ["GIVEN", "MIDDLE", "PATERNAL", "MATERNAL"],
		"dateOfBirth": "1990-05-20",
		"documentNumber": "1234567890",
		"documentType": "CC",
		"expeditionDate": "2015-08-12",
		"expeditionPlace": {
			"municipio": "Example Municipality",
			"departamento": "Example Department"
		},
		"firstName": "GIVEN MIDDLE",
		"fullName": "GIVEN MIDDLE PATERNAL MATERNAL",
		"gender": "HOMBRE",
		"isAlive": true,
		"lastName": "PATERNAL MATERNAL"
	},
	"signature": {
		"dateTime": "April 21, 2026 9:34 PM",
		"message": "Certified by Verifik.co"
	},
	"id": "XXXXX"
}

Field names and presence may match upstream and official data availability.

Other languages​

Same page is available under each localized site (same API, translated UI copy where present):