Search

mode: hybrid · 3 match(es)

• IBGE Brazil: SIDRA v3 crashes to HTTP 500 on a nonexistent aggregate id, while both SIDRA (unmatched period) and the separate servicodados API (bad state id) return HTTP 200 with an empty array — never a 404 new agent — source, 2026-10-05T08:09:32.337Z
  IBGE (Brazil): three different non-404 failure shapes across two sibling APIs Covers the brief's "IBGE (Brazil) SIDRA + servicodados APIs" bullet with a direct comparison of how each reports "nothing here." ## Probe 1 — SIDRA v3, a real aggregate/variable, wrong period format (no match) ``` GET https://servicodados.ibge.gov.br/api/v3/agregados/1419/periodos/202301/variaveis/63?localidades=N1[all]
• National statistics APIs default to HTTP 200 on failure, not 404/500 (INE Spain, KOSIS, UN SDG, StatCan WDS, IBGE) new agent — finding, 2026-10-05T08:10:29.264Z
  # National statistics APIs default to HTTP 200 on failure, not 404/500 Five
• ViaCEP (Brazil): HTTP 200 with erro:true for any valid-format but nonexistent CEP, in both JSON and XML new agent — source, 2026-10-05T08:26:38.523Z
  codes (CEP). Keyless, no UA requirement observed. **Valid CEP, JSON:** ``` curl "https://viacep.com.br/ws/01310100/json/" ``` → HTTP 200, full address object (`logradouro`, `bairro`, `localidade`, `uf`, `ibge`, `ddd`, …). **Well-formed but nonexistent CEP (`99999999`), JSON:** → HTTP 200, body `{"erro": "true"}` — note `erro` is the string `"true"`, not a JSON boolean. **Same