> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usecroma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# VUCE

> What importing goods into Colombia takes, by subpartida arancelaria: the import regime, the tariff decree, how long an import license lasts, every entity that must approve the import and the minimum description the declaration must carry.

Colombia's Ventanilla Única de Comercio Exterior (VUCE), run by the Ministry of Commerce (MinCIT), publishes for every subpartida arancelaria what an import under it requires: the import regime, the decree that sets the tariff, how long an import license or registration lasts, the entities that must give their visto bueno (INVIMA, ICA, FNE and others) with the prior requirement each asks for and the norms behind it, and the minimum description of the goods the import declaration must carry.

Ask with the full 10-digit subpartida. The first ask of a subpartida reads VUCE; later asks within 7 days answer from Croma's stored answer, which is re-read regularly so it follows each new circular.

`POST /co/vuce/tariff/v1` [Lookup](https://docs.usecroma.com/datasets.md#lookups)

What VUCE lists today for one subpartida. The example is medicines for human use, which need a visto bueno from INVIMA and the FNE.

> [!NOTE]
>
> Answers from Croma's copy when it holds a recent answer for the key, otherwise reads the source and keeps the answer. Every response says when the source was last asked (`checked_at`) and where the answer came from (`served_from`).

| Field | Type | Notes |
| - | - | - |
| `tariff_code` | string | **Required.** The full 10-digit subpartida, e.g. `6101909000`. Dots between the groups (`6101.90.90.00`) are accepted; a 4- or 6-digit heading is not. |

```bash theme={"dark"}
curl https://api.croma.run/co/vuce/tariff/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "tariff_code": "3004902900" }'
```

Returns `found`, `tariff_code`, `checked_at` (when VUCE was last asked), `served_from` (`copy`, `upstream` or `stale`) and `tariff`. `tariff` carries `tariff_code`, `chapter`, `heading` and `hs_code` (its first two, four and six digits; `hs_code` is the Harmonized System subheading, the same worldwide), `description` (the subpartida's text in the latest tariff decree), `import_regime` (`LIBRE` or `PREVIA`), `requires_import_license` (`true` for `PREVIA`: importing needs a prior license from MinCIT), `status` (e.g. `Activo`), `legal_basis` (the tariff decree), `license_validity_months`, `note` (trade agreements and quotas that apply, when VUCE lists any), `approvals_regulation` (the circular in force for vistos buenos), `requires_approvals`, `authorities`, `approvals`, `minimum_descriptions`, `minimum_description_sections`, `minimum_description_text`, `additional_information` and `checked_at`.

`authorities` lists each entity that must approve the import once, as `code` (VUCE's, e.g. `GRUPOICA`) and `name` (e.g. `Instituto Colombiano Agropecuario (ICA)`).

Each entry of `approvals` is an entity that must approve the import (visto bueno): `authority` (e.g. `INVIMA`, `GRUPOICA`, `FNE`), `authority_name`, `description` (which goods it covers), `control` (e.g. `VB`), `prior_requirement` (e.g. `Registro Sanitario (RS)`), `prior_requirement_description`, `legal_basis`, `marginal_notes`, `observation` and `group`. An empty list means no entity has to approve the import.

Each entry of `minimum_descriptions` is a control on how the goods are described in the import declaration: `authority`, `control` (e.g. `DM`), `control_description` and `legal_basis`. `minimum_description_text` lists what that description must include, verbatim for the subpartida's whole chapter; `minimum_description_sections` splits it into sections (`title`, e.g. `IX. Confecciones`) and the fields each one requires (`label`, e.g. `Composición porcentual`, and `guidance`).

> [!NOTE]
>
> A subpartida VUCE does not list returns `found: false` with HTTP 200, not an error.

> **[Full reference](https://docs.usecroma.com/api-reference/overview.md)**
>
> Schemas, all response fields, and an interactive playground.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.