Skip to main content

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​

NameValue
Acceptapplication/json
AuthorizationBearer <token>

Parameters​

nametyperequireddescription
documentNumberstringyesPEP number without spaces or punctuation.
expeditionDatestringyesIssue date in DD/MM/YYYY format (e.g. 10/10/2024).

Request​

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);

Response​

{
"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"
}

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.
  • Upstream portal or parsing changes may surface 404 / 500 when no row is found or the source is unavailable.