Mindicador API

Quick workflow

1. Identify the required data granularity.
   Use all indicators, single indicator latest month, single indicator by date, or single indicator by year.

2. Build the correct endpoint path.
   Follow the patterns in references/mindicador-reference.md.

3. Validate indicator slug and date format.
   Use supported slugs exactly and format date as dd-mm-yyyy or year as yyyy.

4. Parse response safely.
   Treat serie as the time series payload and handle missing dates, empty arrays, and transient HTTP/network errors.

5. Report API capability boundaries.
   State that the API is read-only and focused on economic indicators; it does not provide auth, write operations, filtering, pagination, or custom aggregations.

Endpoint selection

• Need a snapshot of all principal indicators: call https://mindicador.cl/api
• Need one indicator recent series: call https://mindicador.cl/api/{tipo_indicador}
• Need one indicator at one date: call https://mindicador.cl/api/{tipo_indicador}/{dd-mm-yyyy}
• Need one indicator for a year: call https://mindicador.cl/api/{tipo_indicador}/{yyyy}

If the user asks for calculations (e.g., monthly average, volatility, conversion tables), fetch the raw series from the API and compute outside the API.

Implementation guidance

• Prefer HTTPS and explicit timeout/retry strategy in clients.
• Normalize decimal/date values in the application layer.
• Use defensive parsing because fields may vary slightly by indicator and query type.
• Cache responses where appropriate to reduce repeated calls.
• Keep examples minimal and production-safe.

Capability assessment checklist

When asked how capable the API is, evaluate explicitly:

• Coverage: indicators and historical ranges are broad for Chile economic data.
• Query flexibility: only four path patterns; no arbitrary server-side filtering.
• Freshness: intended to track Banco Central updates, but treat as external dependency.
• Operational features: no built-in auth, quota metadata, pagination, or write endpoints.
• Fit: strong for indicator lookup and historical reads; limited for analytics workflows unless combined with local processing.

Resources

• Core reference: references/mindicador-reference.md
• Canonical scripts:
• scripts/get_all_indicators.sh
• scripts/get_indicator.sh
• scripts/fetch_indicator.py
• scripts/fetch_indicator.mjs