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

# Entity procedure pages

> Entities' own procedure pages: requirements, fees, where to apply, delivery times and FAQs.

The procedure pages of Colombian entities' own sites, as markdown: what the entity itself says about requirements, fees and how to pay, where to apply, delivery times and its frequently asked questions. They complement the national register of procedures ([Trámites SUIT](/guides/colombia/suit)): an entity's own page is often the most current word on fees, and carries the details the register leaves out.

Today it covers the Ministerio de Relaciones Exteriores (Cancillería: passports, visas, apostilles, consular services) and the Unidad para las Víctimas (the Registro Único de Víctimas, declarations, humanitarian aid, compensation). More entities follow.

Search across every page with free text, or narrow to one entity, and read any page in full.

<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 pages

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

One search over every procedure page of the covered entities, reaching into their full content.

| Field | Type | Notes |
| - | - | - |
| `query` | string | Optional words matched against each page's title and content, e.g. `pasaporte costos`. |
| `site` | enum | Optional: `cancilleria` or `unidad-victimas`. |
| `page` | integer | 1-based page number. Default `1`. |
| `per_page` | integer | Results per page (1-50). Default `10`. |

```bash theme={"dark"}
curl https://api.croma.run/co/gov-pages/search/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "pasaporte costos", "site": "cancilleria" }'
```

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 page's permanent id), `site` (`cancilleria` or `unidad-victimas`), `entity`, `url` (the page on the entity's site), `title` and `modified_at` (when the entity last changed the page, when its site says so).

<Note>
  Search results leave out the page's content. `query` still matches against it; read a page in full with the Colombia Entity Procedure Page endpoint.
</Note>

## One page, in full

`POST /co/gov-pages/page/v1` <a className="dataset-pill" href="/datasets">Dataset</a>

| Field | Type | Notes |
| - | - | - |
| `page_id` | string | **Required.** The page's `id` from a search result, or its `url`. |
| `offset` | integer | First character of the content to return. Pass the previous response's `next_offset` to read on. Default `0`. |
| `limit` | integer | How many characters to return. Most pages fit in one response. Default `200000`. |

```bash theme={"dark"}
curl https://api.croma.run/co/gov-pages/page/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "page_id": "https://www.cancilleria.gov.co/atencion-y-servicio-al-ciudadano/tramites-y-servicios/pasaportes/costos-y-medios-de-pago"
      }'
```

Returns `as_of`, `found`, `page_id` and `page`, which carries everything the search returns plus `content`: the page's content as markdown, links kept, with `text`, `offset`, `total_length`, `has_more` and `next_offset`. Every result carries `id` (the page's permanent id), `site` (`cancilleria` or `unidad-victimas`), `entity`, `url` (the page on the entity's site), `title` and `modified_at` (when the entity last changed the page, when its site says so).

<Note>
  A page the entity no longer publishes 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.