Ir a la app

API versioning

The PASTOR API uses URL-based versioning. Analytical module endpoints use the /api/v3/ prefix. Core account and report endpoints use the /api/v1/ prefix. Non-breaking changes — new optional parameters, new response fields, new endpoint groups — are shipped without a version bump.


Current API

2025-07-28 — Decision history endpoint

New: GET /api/v3/decisiones for retrieving the territorial decision history of a municipality. Parameter: municipio_id (INE code, string).

2025-06-15 — Ecosystem summary endpoint

New: GET /ecosystem for forest ecosystem summaries by municipality. Parameter: municipio_id.

2025-05-01 — Report generation

New: POST /api/v1/report for programmatic PDF report generation. Body: { "municipio_id": "string", "periodo": "YYYY-MM" }. Returns the PDF binary directly.

2025-03-10 — Preventive decision support (M3)

New: GET /api/v3/m3 for preventive decision support data by municipality. Parameter: municipio_id.

2025-01-15 — Ecosystem and biomass module (M10)

New: GET /api/v3/m10 for ecosystem and biomass data by municipality. Parameter: municipio_id.

2024-12-01 — Daily risk analysis (M1)

New: GET /api/v3/m1 for daily wildfire risk analysis. Parameters: municipio_id, date_from, date_to (YYYY-MM-DD). Response fields: risk_score (float 0–1), risk_label (LOW, MEDIUM, HIGH).

2024-10-01 — Narrative risk framing

New: GET /api/v1/framing for narrative risk analysis by municipality. Parameter: municipio_id.

2024-09-01 — User profile and health endpoints

New: GET /api/v1/me for the authenticated user profile. New: GET /health for service status checks.


Breaking changes policy

When a breaking change is necessary:

  • The new behavior ships in a new API version prefix (e.g. /api/v4/).
  • The old version receives at minimum 6 months of bug-fix-only support before deprecation.
  • A deprecation header Deprecation: true is added to all responses from the deprecated version 90 days before retirement.
  • Deprecation dates are announced at pastormap.com/developers/status and via email to all accounts using the affected version.