apicvm.dev
Download llms.txt Get API key

IAN: Brazil's Legacy Annual Information Filing

IAN (Informações Anuais) appears in older CVM download documentation as an annual information category. Developers who search for IAN CVM while reading historical notes or bulk-download manuals usually need modern annual financials — and that product path today is DFP, not IAN.

What is IAN?

IAN was part of the classic CVMWIN / RAD document set alongside ITR and DFP. In older “download múltiplo” docs, clients could request IAN as a document family for annual information packages.

For new integrations, treat IAN as legacy vocabulary. Current standardized annual financial statements that research and agent pipelines want are filed and filtered as DFP (Demonstrações Financeiras Padronizadas).

IAN vs DFP

IAN (legacy framing) DFP (current product focus)
Role Historical annual information category Annual standardized financial statements
Typical use today Interpreting old CVM docs / dumps Audited annual financials via API
apicvm filter Not a supported corpus type type=DFP

If a tutorial still says “download IAN”, map the intent to DFP unless you are deliberately reconstructing a historical dataset from official open-data archives.

How to get annual filings via apicvm

apicvm lists and downloads DFP (and ITR / FRE). Example for PETR4 2024:

export APICVM_KEY='apicvm_...'
export APICVM_URL='https://apicvm.dev'

curl -H "Authorization: Bearer $APICVM_KEY" \
  "$APICVM_URL/v1/documents?ticker=PETR4&type=DFP&year=2024&perPage=20"

Python

import os, requests

BASE = os.environ["APICVM_URL"]
H = {"Authorization": f"Bearer {os.environ['APICVM_KEY']}"}

docs = requests.get(
    f"{BASE}/v1/documents",
    headers=H,
    params={"ticker": "PETR4", "type": "DFP", "year": 2024, "perPage": 20},
).json()["data"]

for d in docs:
    print(d["name"], d["dateRef"], d["id"])

Then download with GET /v1/documents/:id/file or extract text asynchronously when you need markdown pages.

When you still need IAN-labeled archives

Use official CVM open-data / historical bulk channels if your research explicitly requires legacy IAN packages. That ETL path is bulk-oriented — see CSV dumps vs per-filing API.

Current limitations

  • IAN is not part of the apicvm product corpus.
  • Prefer type=DFP for annual statement workflows.
  • Document names inside a DFP year still vary; inspect name and dateRef.

Next steps

Ready to integrate?

Get an API key and start querying Brazilian CVM filings programmatically.

Read the API docs Get API key