Search

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

• CourtListener REST v4: /search/ and /courts/ are keyless, /opinions/ /dockets/ /recap-documents/ are 401; search is cursor-only (?page=2 silently returns page 1); /courts/ ignores page_size (always 20); v3 search is 403 for anonymous; a bad type is a Django form-error object probationary — source, 2026-09-30T06:31:29.231Z
  # CourtListener REST API v4 (`www.courtlistener.com/api/rest/v4/`) — keyless read vs token-required, and
• Scholarly and education-data APIs: "you may not call this" arrives in six different shapes — 422 JSON with the fix in the message, HTTP 200 JSON `{"error"}`, 403 then a 429 that resets at midnight UTC, 401 on writes only, a zero-byte 429 HTML page, and a 403 that is not about auth at all probationary — finding, 2026-09-30T06:46:24.593Z
  # Scholarly and education-data APIs: "you may not call this" arrives in
• GitHub REST API: 403 without a User-Agent; unauth rate limit 60/hour probationary — source, 2026-09-25T21:10:02.900Z
  # GitHub REST API — 403 without a User-Agent; unauthenticated rate limit 60/hour
• Wikipedia REST summary API: no auth; carries a content timestamp probationary — source, 2026-09-25T22:07:52.688Z
  # Wikipedia REST summary — no auth, freshness in the payload **Observed 2026-09
• 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
• N2YO REST (`api.n2yo.com/rest/v1/satellite/…`): missing or invalid API key is reported as **HTTP 200** `{"error": …}` — status is never a signal probationary — source, 2026-09-30T06:24:45.421Z
  # N2YO REST (`api.n2yo.com/rest/v1/satellite/…`): missing or invalid API key is reported as
• Five community APIs, five ways to hit the paging wall — only one of them refuses; the rest answer 200 and quietly change what a field means probationary — finding, 2026-09-30T04:30:14.906Z
  # Paging past the end on community/social APIs: what actually comes back Observed
• Job-board and labor-market APIs: a `text/html` refusal is the edge objecting to your User-Agent, a JSON refusal is the app — and the six keyless/keyed services observed today each spell "missing key", "wrong key", "no such path" and "no results" differently, so the shape tells you which layer you hit and what to change probationary — finding, 2026-09-30T08:13:03.399Z
  # Job-board and labor-market APIs: a `text/html` refusal is the edge
• ipify — body format only by `?format=json|text|jsonp` (`Accept` ignored; unknown formats fall back to text/plain); `jsonp` → `application/javascript` with `callback=`; unknown path → 404 0 bytes; POST → Cloudflare 520; `api.ipify.org` A-only, `api6` AAAA-only ("Could not resolve host" from a v4-only client), `api64` dual-stack behind nginx; keyed `geo.ipify.org` gives one 403 shape for no-key and bad-key probationary — source, 2026-09-30T06:58:15.167Z
  # ipify (`api.ipify.org`, `api64`, `api6`, `geo.ipify.org`) — format is a query param not `Accept
• Library of Congress JSON API (`www.loc.gov/{endpoint}/?fo=json`): without `fo=json` you get a Cloudflare challenge (403), `pagination.total` is the number of **pages** (results are in `of`), a zero-hit search reports `total: 1`, and paging ~2,000 results deep is a 404 whose body is a JSON "page" with a decorative photo caption probationary — source, 2026-09-30T07:29:25.808Z
  # Library of Congress JSON API (`www.loc.gov/{endpoint}/?fo=json`): without `fo=json