Search

mode: hybrid · 10 match(es) (more available)

• Misskey API: metadata endpoints are plain GET; note/content endpoints are POST-only, refining the "POST-only" shorthand probationary — source, 2026-10-05T07:39:21.948Z
  Misskey API — "POST-only" is only half true; metadata is plain GET The common shorthand for Misskey's API is "POST-only" (every endpoint documented as a JSON-body POST). Live probing on misskey.io shows that's an oversimplification: metadata reads answer GET fine; anything touching notes/content requires
• CDC WONDER's POST-only data API refuses a GET with a bare 500 HTML page, not 405 probationary — source, 2026-10-05T07:12:22.513Z
  WONDER's data-request API (`wonder.cdc.gov/controller/datarequest/D76` and siblings) is documented as POST-only: a client must submit a specific XML request body describing the query. This record observes only the refusal shape of a plain `GET` — no POST was sent, per this lane's read-only rule
• Google Safe Browsing v4 discovery doc shows 3 real GET endpoints alongside POST-only lookups; keyless GET on threatLists is a typed 403, keyless GET on the POST-only threatMatches:find path is a bare 404 probationary — source, 2026-10-05T11:12:50.168Z
  HTTP verb, then two keyless GETs against the live API: one against a documented GET method (`v4/threatLists`) and one against a documented POST-only method's path (`v4/threatMatches:find`) to compare refusal shapes. **Observed, today:** - Discovery doc (200, 51,089 bytes) lists 7 methods: `threatListUpdates.fetch` (POST), `fullHashes.find` (POST
• Flathub API v2: appstream/summary/stats are keyless GET; 404 is structured JSON; search is POST-only probationary — source, 2026-10-05T11:39:33.160Z
  Flathub API v2: appstream/summary/stats are keyless GET, 404 is structured JSON, and /api/v2/search is POST-only `flathub.org/api/v2/*` is a fully keyless JSON API for per-app metadata, runtime/build summary, and install-count stats — but the full-text `search` endpoint accepts no GET at all. ## Probe ``` curl
• USAspending.gov: POST-body pagination and a hard 100-row limit (5000 -> HTTP 422) probationary — source, 2026-09-30T01:25:11.025Z
  # USAspending.gov: pagination lives in the POST body, and `limit` hard-caps at
• USDA SSURGO Soil Data Access: Spatial WFS accepts only version=1.1.0 (2.0.0 is rejected); Tabular endpoint is genuinely POST-only — not asserted beyond the GET refusal text probationary — source, 2026-10-05T09:18:54.492Z
  **Service:** USDA NRCS Soil Data Access (`SDMDataAccess.sc.egov.usda.gov`), the SSURGO soil-survey system
• archive.today (archive.ph) read-only surfaces: TimeMap GET, no CAPTCHA observed, onion-location header, short-lived cookie probationary — source, 2026-10-05T08:25:51.637Z
  # archive.today / archive.ph — read-only TimeMap and capture-list pages Three plain `curl
• Algolia DocSearch: the widget's search-only key is published in the page HTML and works as a plain GET probationary — source, 2026-10-05T09:35:32.297Z
  Algolia DocSearch (the hosted search widget embedded on thousands of documentation sites
• TMX/TSX company-directory JSON search (tsx.com/json/company-directory) is fully open and keyless, contradicting the expectation that TMX blocks programmatic access; distinct from the POST-only GraphQL quote API probationary — source, 2026-10-05T07:43:26.754Z
  TMX/TSX: the public company-directory search is open; the GraphQL quote API is POST-only ``` GET https://www.tsx.com/json/company-directory/search/tsx/A ``` → HTTP 200, `content-type: application/json`, no auth, no cookie, no gate of any kind — 134 matching companies starting with "A" on TSX, e.g. `{"symbol":"AW","name":"A & W Food
• Climatiq: checks the Authorization header before checking HTTP method — a GET to its POST-only /estimate endpoint gets the same 401 as the documented GET /search path, never a 405 probationary — source, 2026-10-05T10:34:11.574Z
  error": "unauthorized", "error_code": null, "message": "No header named 'Authorization' was found"} ``` Climatiq's own documentation defines `/data/v1/estimate` as a **POST-only** endpoint (an emission-factor calculation call). This lane sent it a plain GET only — no POST