Superfinanciera

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

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" }'

The whole source, organized and ready to query: this endpoint answers in milliseconds, at any hour, the same way every time. Every response carries as_of: how current the data is.

Returns as_of (how current the data is), the applied filters, total (matches across every page), 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.

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.

One act

POST /co/superfinanciera/regulation/v1

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

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" }'

The whole source, organized and ready to query: this endpoint answers in milliseconds, at any hour, the same way every time. Every response carries as_of: how current the data is.

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.

An id the register does not carry returns found: false with HTTP 200, not an error.

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`).

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

This lookup can take longer than a typical request. It’s an async job. 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.

Full reference

Schemas, all response fields, and an interactive playground.

Get Started

Countries

Search the normative register

One act

Request

Response

Full reference

​Search the normative register

​One act

​Request

​Response

Full reference

Search the normative register

One act

Request

Response