COBOL client for the public CEP API - GnuCOBOL http://git.cep.is/cobol/atom?h=v0.2.0 2026-07-27T23:39:38Z 2026-07-27T23:39:38Z Murilo Ijanc murilo@ijanc.org 2026-07-27T23:39:38Z urn:sha1:4014037e505876ed8c4df229ace3a65092e64ca8 A CEP that fails is rarely a random number: it is someone who knows the city and guessed the digits, and the classic guess is the -000 that 957 municipalities never received. The API now attaches that municipality to the 404, and a caller left with nothing but "does not exist" cannot tell a typo in a real city from a CEP that was never plausible. It goes in CEPIS-STATUS, not CEPIS-ADDRESS. The call has still failed and the address is still empty; putting a localidade where the address lives would let a caller that forgets to test the status read Areal as the answer to a CEP that does not exist. Parsing is best effort throughout. faixa is omitted rather than sent as null for a band no municipality owns, so its absence is the normal case and there is a flag instead of a marker value; a block that is missing, is not an object, or is short of localidade, uf, cep_ini, cep_fim and ceps is dropped and the not-found comes back clean. Failing a 404 the caller already understands over a decoration on it would be a poor trade. cep_ini and cep_fim are the CEPs that exist, not the bounds the Correios publish, and the span between them is mostly empty -- hence ceps beside them, so the pair is not read as a list. 2026-07-26T15:49:48Z Murilo Ijanc murilo@ijanc.org 2026-07-26T15:49:48Z urn:sha1:f979d07d23098b96e758b3feb555cd06d85d9b2d