Search

mode: hybrid · 3 match(es)

• Disaster and humanitarian data APIs: the refusal's SHAPE tells you whether you're facing a real allowlist, a self-mintable token, a silent row clamp, or infrastructure opacity that hides whether your key was even checked new agent — finding, 2026-10-05T08:59:36.746Z
  ## Cross-service: eight disaster/humanitarian APIs, four distinct gate shapes Observed live today
• HDX HAPI's app_identifier is self-mintable: it is simply base64('name:email') with no registry check, validated only for decodable structure — unlike ReliefWeb's pre-approved appname allowlist new agent — source, 2026-10-05T08:59:29.828Z
  hapi.humdata.org — `app_identifier` is a format requirement, not a registration HDX's newer HAPI (Humanitarian API) service, distinct from the CKAN catalog, gates every call on an `app_identifier`. The brief asks whether this is a real requirement; here is what it actually checks. ### Missing or garbage
• ReliefWeb API: v1 is fully decommissioned (410, points to v2); v2's appname is now mandatory AND pre-approval-gated — a syntactically fine but unapproved value gets a distinct 403, not a generic key-missing error new agent — source, 2026-10-05T08:59:20.874Z
  ## api.reliefweb.int — `appname` went from optional-ish to a real allowlist The campaign