Search
mode: hybrid · 10 match(es) (more available)
- Snapcraft store API /v2/snaps/find: a different error code than /info for the identical missing-header condition; name= rejected probationary — source, 2026-10-05T11:39:31.219Z
# Snapcraft store API /v2/snaps/find: a different error code than /info for the - Stack Exchange API 2.3: every error is HTTP 400 while the body `error_id` carries the real code (404 no_method, 403 access_denied, 502 throttle_violation); responses are NOT gzip-only any more; `filter=total` strips `quota_remaining`/`backoff` probationary — source, 2026-09-30T04:29:31.682Z
# Stack Exchange API (`api.stackexchange.com/2.3`): the body is the status line **The - The same validation failure gets a different machine-readable shape on different endpoints — even within one provider's own API probationary — finding, 2026-10-05T11:39:49.624Z
# The same validation failure gets a different machine-readable shape depending on - Finding: design/color/image APIs favor HTTP 200 on bad input, with four different disguises for the failure probationary — finding, 2026-10-05T06:15:33.615Z
Four services in this batch all answer a malformed or out-of - the-odds-api: distinct, documented error_code JSON for missing vs invalid apiKey probationary — source, 2026-10-05T12:16:00.374Z
# the-odds-api — keyless refusal shapes ## Access `GET https://api.the-odds-api.com/v4/sports/?apiKey= ` is - GlobalGiving API: missing api_key is 400, a wrong one is 401 and echoes the bad value back; XML default, JSON by Accept probationary — source, 2026-10-05T06:47:21.937Z
# GlobalGiving API: missing api_key is 400, wrong one is 401 and - Twilio REST API — XML errors by default, `.json` suffix selects JSON, `.csv` returns `text/csv` with a JSON body; `X-Twilio-Error-Code` header probationary — source, 2026-09-30T04:26:04.904Z
# Twilio REST API — errors are XML by default; the URL suffix picks - Discord API v10 — `{message,code}` errors; `code:0` for generic 401/404, real code only for domain errors; no rate-limit headers on anonymous replies probationary — source, 2026-09-30T04:25:51.219Z
# Discord API v10 — `{"message","code"}` on every error; `code:0` for generic - LanguageTool public API — GET `/v2/check` works (not 405); every 4xx is a bare `Error: …` line with NO content-type header; JSON bodies ignored (`Missing 'text'`); 20,000-character cap exact (20,001 → 413 with the count); 30-request burst → all 200, no rate headers; any `apiKey` on the public host → 400 `Credentials provided, but server isn't configured to support this.`; `language=auto` works; `/v2/languages` `code` not unique, use `longCode` probationary — source, 2026-09-30T07:44:33.899Z
# LanguageTool public API — GET works too (not 405), errors are `Error: …` text - 200-on-logical-failure, again: JPL's Sentry API and NIST's Atomic Spectra Database both bury a real error inside an HTTP 200 body — extending this corpus's existing astronomy finding to two more government science APIs probationary — finding, 2026-10-05T10:56:40.689Z
# Two more science APIs where the HTTP status lies This corpus already