Skip to main content

Colombia — PPT (Temporary Protection Permit)

Verifik validates PPT (Permiso de Protección Temporal) records published by Migración Colombia for KYC, eligibility, and compliance workflows.

What this API returns

  • Status (e.g. VIGENTE) and key dates, including expedition and expiration
  • Structured name fields and PPT document metadata
  • Responses are signed and may be cached

API reference

Endpoint

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

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
documentNumberstringyesPPT number without spaces or punctuation.
expeditionDatestringyesIssue date in DD/MM/YYYY format (e.g. 07/03/2022).

Request

import axios from "axios";

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

Response

{
"data": {
"arrayName": ["JUAN", "MIGUEL", "CAMERO", "MORALES"],
"documentNumber": "2081381",
"documentType": "PPT",
"expeditionDate": "07/03/2022",
"expirationDate": "30/05/2031",
"firstName": "JUAN MIGUEL",
"fullName": "JUAN MIGUEL CAMERO MORALES",
"lastName": "CAMERO MORALES",
"status": "VIGENTE"
},
"signature": {
"dateTime": "May 13, 2025 11:52 PM",
"message": "Certified by Verifik.co"
},
"id": "JD24J"
}

Features

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

Use cases

  • Humanitarian and social programs that require proof of temporary protection status
  • Employer and financial onboarding where Colombian immigration checks apply

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.