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

# Superfinanciera

> Search every Circular Externa, Carta Circular and Resolución the Superintendencia Financiera de Colombia has issued since 2005, and track a jurisdictional complaint.

Two things the Superintendencia Financiera de Colombia publishes. The first is
its normative register: every Circular Externa, Carta Circular and Resolución
issued since 2005, searchable across kinds and years in one query, with the
official description of what each act does and a link to the act itself. The
second is the action history of a jurisdictional complaint (demanda) filed
against a supervised entity.

## Search the normative register

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

One search across circulares externas, cartas circulares and resoluciones from 2005 to today, which the Superintendencia's own site does not offer.

| Field | Type | Notes |
| - | - | - |
| `query` | string | Optional words to match in the official description of the act, its citation and its number. |
| `kind` | enum | `circular_externa` (instructions binding on supervised entities), `carta_circular` (informative, creates no obligation), `resolucion` (an administrative act), or `any`. Default `any`. |
| `year` | integer | Optional year the act was issued, 2005 or later. Omit or pass 0 to search every year. Default `0`. |
| `number` | string | Optional exact number. Leading zeros are optional: `7` and `007` find the same act. |
| `bulletin` | string | Optional issue of the Boletín del Ministerio de Hacienda y Crédito Público, Capítulo Superintendencia Financiera. |
| `issued_from` | string | Optional: only acts issued on or after this date, `yyyy-mm-dd`. |
| `issued_to` | string | Optional: only acts issued on or before this date, `yyyy-mm-dd`. |
| `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/superfinanciera/regulations-search/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "riesgo de crédito", "kind": "circular_externa" }'
```

Returns `as_of` (how current the data is), the applied filters, `total` and
`total_is_exact`, `page`, `per_page`, `total_pages`, `count` and
`results[]`, most recent first. Every result carries `id`, `kind`, `number` as the register prints it,
`number_key` (the same number with leading zeros dropped), `year`, `issued_at`,
`title` (how the act is cited), `description` (what the act does, in the
Superintendencia's own words), `bulletin` (the issue of the Boletín del
Ministerio de Hacienda y Crédito Público it was published in), `document_url`,
`attachments[]` and `official_url`.

<Note>
  The whole register, from 2005 to this week's acts, ready to query. The acts
  themselves stay where the Superintendencia publishes them: `document_url` is
  the address to read one, and the file format follows the era it was issued in.
</Note>

## One act

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

| Field | Type | Notes |
| - | - | - |
| `regulation_id` | string | **Required.** The `id` from the search results: kind, year and number, e.g. `ce:2026:7`, `cc:2026:56`, `res:2026:1195`. |

```bash theme={"dark"}
curl https://api.croma.run/co/superfinanciera/regulation/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "regulation_id": "ce:2026:7" }'
```

Returns `as_of`, `found`, `regulation_id` and `regulation`. Every result carries `id`, `kind`, `number` as the register prints it,
`number_key` (the same number with leading zeros dropped), `year`, `issued_at`,
`title` (how the act is cited), `description` (what the act does, in the
Superintendencia's own words), `bulletin` (the issue of the Boletín del
Ministerio de Hacienda y Crédito Público it was published in), `document_url`,
`attachments[]` and `official_url`.

<Note>
  An id the register does not carry returns `found: false` with HTTP 200, not an
  error.
</Note>

## Request

`POST /co/superfinanciera/complaints/v1`

| Field | Type | Notes |
| - | - | - |
| `document_number` | string | **Required.** 5-20 digits. |
| `filing_number` | string | **Required.** Exactly 10 digits (the complaint's `numeroRadicación`). |

```bash theme={"dark"}
curl https://api.croma.run/co/superfinanciera/complaints/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "document_number": "1234567890", "filing_number": "2024051440" }'
```

## Response

`actions` is the complaint's action history (actuaciones), one entry per step,
oldest first. A filing with nothing against it returns an empty array.

| Field | Notes |
| - | - |
| `action_date` | Date of the action (`yyyy-mm-dd`), or `null`. |
| `record_id` | The action's record id, e.g. `2024051440-001-000`. |
| `party` | Party or office involved (petitioner, court unit, or the entity). |
| `action` | The action performed, e.g. `AUTO ADMISORIO VERBAL SUMARIO`. |
| `attachments` | Documents filed with the action, or `null`. |
| `annexes` | Annexes to the action, or `null`. |

<Note>
  This lookup can take longer than a typical request. It's an
  [async job](/async-jobs). By default the request waits inline and returns
  `{ data }`, or you can poll / use a `callback_url`. No matches returns an
  empty `actions` array, 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.