Colombia — RETHUS (health professionals registry)

Verifik confirms identity against RETHUS (Registro Único Nacional de Talento Humano en Salud) using documentType and documentNumber. The flow first resolves the person via the Colombian citizen lookup, then queries RETHUS for registry status, academic qualifications, and social security / benefit (SSO) rows when the source returns them.

Use this endpoint for credentialing, compliance, and workforce checks where RETHUS data is permitted.

What this API returns

• Identity fields from the underlying citizen match (name parts, document type/number)
• rethus.status — registry status text from the RETHUS result grid
• rethus.academic — array of academic/professional rows (type, degree origin, profession, dates, entity, etc.) when present
• rethus.dataSSO — benefit / modality / entity rows when present
• A signed Verifik response

API reference

Endpoint

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

Same fields may be sent in a POST JSON body. GET uses query parameters as below.

Query-only summary: documentType, documentNumber.

Headers

Name	Value
Accept	application/json
Authorization	Bearer <token>

Parameters

name	type	required	description
documentType	string	yes	One of CC, CE, PPT.
documentNumber	string	yes	Document number without spaces or punctuation (length 5–15).

Request

JavaScript

import axios from "axios";

const { data } = await axios.get("https://api.verifik.co/v2/co/cedula/rethus", {
	params: {
		documentType: "CC",
		documentNumber: "123456789",
	},
	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/rethus"
headers = {"Accept": "application/json", "Authorization": f"Bearer {os.getenv('VERIFIK_TOKEN')}"}
params = {"documentType": "CC", "documentNumber": "123456789"}
r = requests.get(url, headers=headers, params=params)
print(r.json())

Response

200

{
	"data": {
		"documentType": "CC",
		"documentNumber": "123456789",
		"firstName": "MARIA",
		"lastName": "GOMEZ LOPEZ",
		"fullName": "MARIA GOMEZ LOPEZ",
		"rethus": {
			"status": "ACTIVO EN RETHUS",
			"academic": [
				{
					"type": "Pregrado",
					"originDegree": "Nacional",
					"profession": "MÉDICO GENERAL",
					"startDate": "01/01/2010",
					"administrativeAct": "…",
					"entity": "…"
				}
			],
			"dataSSO": [
				{
					"typeBenefit": "…",
					"typePlaceBenefit": "…",
					"placeBenefit": "…",
					"startDate": "…",
					"endDate": "…",
					"modalityBenefit": "…",
					"programBenefit": "…",
					"entity": "…"
				}
			]
		}
	},
	"signature": {
		"dateTime": "January 16, 2024 3:44 PM",
		"message": "Certified by Verifik.co"
	}
}

404

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

409

{
	"code": "MissingParameter",
	"message": "documentType must be one of [CC, CE, PPT]"
}

Features

• Document types accepted by validation: CC, CE, PPT
• No issue date required (unlike some other Colombian endpoints)
• GET and POST share the same handler

Use cases

• Hospital and clinic credentialing
• Regulatory and insurance checks on health professionals

Notes

• RETHUS is queried after a successful citizen match; if the person cannot be resolved upstream, you may see 404 or other errors.
• rethus.academic and rethus.dataSSO may be empty arrays when the portal returns no rows.
• Captcha or source outages can surface as 5xx or Endpoint_out_of_service-style errors depending on handling.
• Treat responses as sensitive personal data; comply with Colombian health-privacy rules.