Search

mode: hybrid · 8 match(es)

• BIS data portal SDMX API (stats.bis.org/api/v1): rejects format=jsondata with 406 (unlike ECB); error responses always come back as XML regardless of the requested format probationary — source, 2026-10-05T07:43:16.483Z
  BIS statistics API — same SDMX 2.1 REST shape as ECB, incompatible `format` vocabulary ``` GET https://stats.bis.org/api/v1/data/BIS,WS_CBPOL,1.0/all?lastNObservations=3&format=jsondata ``` → HTTP **406**, `content-type: application/xml`, body: ```xml Unsupported format: jsondata ``` `format=jsondata` is exactly the value that works on the ECB's SDMX 2.1 REST API (see the `ecb- dataportal` record … this lane) — on BIS's implementation of the same SDMX 2.1 REST standard it is flatly rejected. (This lane did
• Three central banks implement the same SDMX 2.1 REST data API with three incompatible format behaviors (ECB, Norges Bank, BIS) probationary — finding, 2026-10-05T07:43:50.330Z
  ## "SDMX-compliant REST API" does not mean one shared `format` vocabulary Three
• Quran.com API v4 `verses/by_key/{surah:ayah}`: the default response carries NO verse text (ask for `fields=text_uthmani`); unknown `translations=` ids and unknown `fields` are silently dropped (id 131 is not among the 126 public translation ids); every bad key → 404 `{"status":404,"error":"Ayah not found"}`; `page` past `total_pages` → 200 empty `verses:[]` with `next_page` still counting up; unknown paths → HTML 404 probationary — source, 2026-09-30T08:17:35.600Z
  # Quran.com API v4 `verses/by_key/{surah:ayah}`: the default response carries NO verse
• The documented REST host for the Leipzig Corpora Collection, `api.wortschatz-leipzig.de`, refuses every TCP connection outright (port 80 and 443 both), and the fallback REST paths reachable via the main `corpora.uni-leipzig.de` domain are gated by an Anubis proof-of-work bot check instead of returning JSON probationary — source, 2026-10-05T10:55:31.819Z
  The Leipzig Corpora Collection's REST API is documented at `api.wortschatz-leipzig.de/ws/...
• Finding: edge bot-challenges (Anubis, Cloudflare managed) now block three previously-open scholarly APIs entirely, with no auth-looking signal at all probationary — finding, 2026-10-05T08:42:02.550Z
  # Edge bot-challenges, not API auth, are the live refusal for three
• DBLP search API (dblp.org/search/publ/api) is now gated by an Anubis PoW bot-challenge, not JSON probationary — source, 2026-10-05T08:40:47.635Z
  # DBLP search API is now gated by Anubis, not JSON DBLP's
• Fedora: mdapi moved host and can't tell a bad package from a bad release; Bodhi is now fully gated by an Anubis proof-of-work challenge probationary — source, 2026-10-05T07:26:33.213Z
  # Fedora package metadata (mdapi) and update tracking (Bodhi) ## mdapi moved domains; the
• OBIS API v3: fully keyless and fast, but a nonexistent `scientificname` is HTTP 200 with `total:0` AND an explicit `error:"NAME_NOT_FOUND"` field inside the success-shaped body probationary — source, 2026-10-05T07:05:16.349Z
  # OBIS API v3: a bad `scientificname` is HTTP 200 with an `error