Documentation
incode.com
  1. Foundations
  2. Government Verification Sources
  3. Colombia

Error Code Changes for Colombia

This page details changes that were made in June 2026.

Error code definitions and response statuses for the Colombia Government Verification module changed in June 2026. These changes improve result explainability, reduce ambiguity, and make it easier to interpret session outcomes in Dashboard and via API responses.

⚠️

Action Required

If your implementation uses the impacted error codes for downstream decisioning logic or alerting, please review the status changes carefully and update your logic accordingly.

1. Status Changes: FAIL → UNKNOWN for select error codes.

Several error codes that previously returned FAIL status now return UNKNOWN. This more accurately reflects that these outcomes are not a definitive verification failure; rather, they indicate the verification could not be completed due to missing inputs, configuration issues, or connectivity problems.

Error CodeDescriptionOld StatusNew Status
NOT_ENOUGH_DATAOne or more required fields are missing or invalid.FAILUNKNOWN
CONNECTION_ERRORError occurred while trying to connect to the provider or during provider processing.FAILUNKNOWN

If you prefer to continue failing sessions that now return UNKNOWN (e.g., CONNECTION_ERROR during a provider outage), you can configure this via Business Rules without any code changes on your end.

2. New Error Codes & Mapping

The following error codes can now be returned. Previously, these scenarios were grouped under broader codes and now map to more specific codes to provide more precision in result handling.

New CodeDescriptionStatus
PROVIDER_UNAVAILABLEProvider has been intentionally disabled.UNKNOWN
PROVIDER_NOT_CONFIGUREDProvider is not configured or is incorrectly configured for this flow.UNKNOWN
USER_NOT_FOUNDThe document was not found in the government database.FAIL

3. Updated Behavior for VALIDATION_ERROR

VALIDATION_ERROR continues to return FAIL, but it is now applied more precisely to only include genuine verification failures (such as a document being found but in a canceled/not-valid state). Scenarios that are not true verification failures (connectivity, availability, missing input data) are now mapped individually instead of being grouped under VALIDATION_ERROR.

Error Code Table

Reason CodeDescriptionStatus
PROVIDER_UNAVAILABLEProvider has been intentionally disabled.UNKNOWN
PROVIDER_NOT_CONFIGUREDProvider is not configured or is incorrectly configured for this flow.UNKNOWN
NOT_ENOUGH_DATAOne or more required fields are missing or invalid.UNKNOWN
CONNECTION_ERRORError occurred while trying to connect to the provider or during provider processing.UNKNOWN
USER_NOT_FOUNDThe document was not found in the government database.FAIL
VALIDATION_ERRORDocument exists in the government database but is an invalid status.FAIL

What's Not Changed

  • The API interface is unchanged. Error codes continue to be returned in the same fields and the same response structure. This update is fully backwards compatible; no integration changes are required.
  • Error codes remain available in Business Rules. All error codes (including newly distinguished ones) continue to be exposed in Business Rules, so you can configure FAIL or UNKNOWN handling as needed.