> ## 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.

# Colombian government procedures (SUIT)

> Every procedure Colombia's public entities offer: requirements, fees, steps, channels and points of service.

The Sistema Único de Información de Trámites (SUIT), run by Función Pública, is the official register of every procedure a Colombian public entity offers to citizens and companies: from a passport or a duplicate cédula to a municipal permit. gov.co shows each one as a procedure page numbered `T` plus its número único.

Each procedure here comes with its entity, the entity's order and municipality, whether it can be done online, and its full information: purpose, audience, every step with its documents, conditions, channels, forms and fees, exceptions, legal basis and points of service. `modified_at` says when the entity last updated it.

Search across national and territorial entities with free text that reaches into requirements and fees, or narrow by order, entity or DANE department and municipality.

<Note>
  The whole source, organized and ready to query: every endpoint on this page answers in milliseconds. Every response carries `as_of`: how current the data is. [How datasets work](/datasets).
</Note>

## Search the procedures

`POST /co/suit/procedures-search/v1` <a className="dataset-pill" href="/datasets">Dataset</a>

One search over every procedure of every public entity, national and territorial, reaching into requirements and fees.

| Field | Type | Notes |
| - | - | - |
| `query` | string | Optional words matched against the name, the entity, the purpose and the procedure's full information, e.g. `pasaporte` or `duplicado cédula`. |
| `order` | enum | Optional: `national` for national entities, `territorial` for departments, districts and municipalities, `any` for both. Default `any`. |
| `entity_code` | string | Optional: only procedures of the entity with this code, as `entity_code` gives it in a result, e.g. `5396` for the Registraduría. |
| `department_code` | string | Optional two-digit DANE code of the entity's department, e.g. `05` for Antioquia. |
| `municipality_code` | string | Optional five-digit DANE code of the entity's municipality, e.g. `11001` for Bogotá. |
| `page` | integer | 1-based page number. Default `1`. |
| `per_page` | integer | Results per page (1-50). Default `20`. |

```bash theme={"dark"}
curl https://api.croma.run/co/suit/procedures-search/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "duplicado cédula", "order": "national" }'
```

Returns `as_of` (how current the data is), the applied filters, `total` and `total_is_exact`, `page`, `per_page`, `total_pages`, `count` and `results[]`, best match first when `query` is set. Every result carries `id` (the procedure's número único, which gov.co shows as `T44`), `number`, `name`, `purpose`, `result` (what the person obtains), `time_to_obtain`, `procedure_class` (`UNICO` for one entity's own procedure, `MODELO` for a standard one many entities offer), `state`, `version`, `entity_code`, `entity_name`, `entity_order` (`NACIONAL` or `TERRITORIAL`), `entity_level` (`MUNICIPAL`, `DEPARTAMENTAL` or `DISTRITAL` for territorial entities), `department_code` and `municipality_code` (DANE), `municipality_name`, `online` (`TOTALMENTE`, `PARCIALMENTE` or `NO`), `online_url`, `manual_url`, `entity_url`, `modified_at` (when the procedure's information was last updated), `created_at` and `official_url` (the procedure on gov.co).

<Note>
  Search results leave out the procedure's full information. `query` still matches against it, so a requirement or a fee finds the procedure; read it in full with the Colombia Procedure endpoint.
</Note>

## One procedure, in full

`POST /co/suit/procedure/v1` <a className="dataset-pill" href="/datasets">Dataset</a>

| Field | Type | Notes |
| - | - | - |
| `procedure_id` | string | **Required.** The procedure's número único, e.g. `44`, also as `T44`, or its `official_url` on gov.co. |
| `offset` | integer | First character of the text to return. Pass the previous response's `next_offset` to read on. Default `0`. |
| `limit` | integer | How many characters of the text to return. Most procedures fit in one response. Default `200000`. |

```bash theme={"dark"}
curl https://api.croma.run/co/suit/procedure/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "procedure_id": "T44" }'
```

Returns `as_of`, `found`, `procedure_id` and `procedure`, which carries everything the search returns plus `content`: the procedure's full information as markdown (purpose, audience, every step with its documents, conditions, channels, forms and fees, exceptions, legal basis and points of service), with `text`, `offset`, `total_length`, `has_more` and `next_offset`. Every result carries `id` (the procedure's número único, which gov.co shows as `T44`), `number`, `name`, `purpose`, `result` (what the person obtains), `time_to_obtain`, `procedure_class` (`UNICO` for one entity's own procedure, `MODELO` for a standard one many entities offer), `state`, `version`, `entity_code`, `entity_name`, `entity_order` (`NACIONAL` or `TERRITORIAL`), `entity_level` (`MUNICIPAL`, `DEPARTAMENTAL` or `DISTRITAL` for territorial entities), `department_code` and `municipality_code` (DANE), `municipality_name`, `online` (`TOTALMENTE`, `PARCIALMENTE` or `NO`), `online_url`, `manual_url`, `entity_url`, `modified_at` (when the procedure's information was last updated), `created_at` and `official_url` (the procedure on gov.co).

<Note>
  Fees and requirements are as the entity last published them in the register; `modified_at` says when. A procedure's own entity page can be more recent.
</Note>

<Note>
  A número único the register does not hold returns `found: false` with HTTP 200, not an error.
</Note>

<Card title="Full reference" icon="code" href="/api-reference/overview">
  Schemas, all response fields, and an interactive playground.
</Card>


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