Colombia — PEP (Special Stay Permit)

Verifik validates PEP (Permiso Especial de Permanencia) records published by Migración Colombia for KYC, eligibility, and compliance workflows.

What this API returns

• Status (e.g. VIGENTE / VENCIDO) and key dates, including expedition and expiration where provided
• Structured name fields, PEP document metadata, and Venezuelan identification when returned by the source
• Responses are signed and may be cached

API reference

Endpoint

GET https://api.verifik.co/v2/co/foreigner-id/pep

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>

Document requirements

Who is this for? Venezuelan nationals in Colombia who hold a Permiso Especial de Permanencia (PEP) — an immigration permit, not “politically exposed person” AML screening (see Colombian PEP (AML) for that product).

Field	Guidance
documentNumber	PEP permit number, digits only. In Colombia this number is always 15 digits. Send all 15 digits without spaces or punctuation. Example: 123456789012345.
expeditionDate	Issue date on the PEP, format DD/MM/YYYY (e.g. 10/10/2024). Required.

Full comparison: Colombia identity documents guide.

Parameters

name	type	required	description
documentNumber	string	yes	PEP permit number, digits only. 15 digits (fixed length in Colombia). Example: 123456789012345.
expeditionDate	string	yes	Issue date in DD/MM/YYYY format (e.g. 10/10/2024). Must match the document.

Request

JavaScript

import axios from "axios";

const { data } = await axios.get("https://api.verifik.co/v2/co/foreigner-id/pep", {
	params: {
		documentNumber: "123456789",
		expeditionDate: "10/10/2024",
	},
	headers: {
		Accept: "application/json",
		Authorization: `Bearer ${process.env.VERIFIK_TOKEN}`,
	},
});
console.log(data);

Python

import os, requests

url = "https://api.verifik.co/v2/co/foreigner-id/pep"
headers = {"Accept": "application/json", "Authorization": f"Bearer {os.getenv('VERIFIK_TOKEN')}"}
params = {"documentNumber": "123456789", "expeditionDate": "10/10/2024"}
r = requests.get(url, headers=headers, params=params)
print(r.json())

Response

200

{
	"data": {
		"arrayName": ["MATEO", "VERIFIK"],
		"documentNumber": "123456789012345",
		"documentType": "PEP",
		"expirationDate": "08/08/2018",
		"firstName": "MATEO",
		"fullName": "MATEO VERIFIK",
		"identification": "17609583",
		"lastName": "VERIFIK",
		"status": "VENCIDO"
	},
	"signature": {
		"dateTime": "August 22, 2023 8:02 PM",
		"message": "Certified by Verifik.co"
	},
	"id": "tnlkb"
}

404

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

409

{
	"code": "MissingParameter",
	"message": "expeditionDate must be a valid date in DD/MM/YYYY format"
}

Features

• Official PEP lookup against Migración Colombia’s public consultation flow
• Validity and lifecycle fields when returned by the source

Use cases

• Employment, banking, and services for Venezuelan nationals with PEP in Colombia
• Humanitarian and social programs that require proof of stay status

Notes

• expeditionDate must match DD/MM/YYYY; wrong formats typically return 409.
• GET and POST are both routed to the same handler; use POST if you prefer a JSON body.
• This PEP is the immigration permit (Permiso Especial de Permanencia), not AML “politically exposed persons” — see Colombian PEP (AML).
• See the Colombia identity documents guide for the 15-digit format and endpoint routing.
• Upstream portal or parsing changes may surface 404 / 500 when no row is found or the source is unavailable.