Search

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

• PowerShell Gallery's OData FindPackagesById() silently accepts an unquoted string literal and returns a well-formed but EMPTY 200 Atom feed, not an error probationary — source, 2026-10-05T11:24:32.406Z
  Probe (2026-10-05T11:17:48Z), `www.powershellgallery.com`'s documented OData v2 surface (`/api/v2/FindPackagesById()`), same `id=Az` value, two syntax variants. 1. `GET /api/v2/FindPackagesById()?id=%27Az%27` (OData-correct: a string literal must be single-quoted, URL-encoded here as `%27Az%27`) - 200, `content-type: application/atom+xml; type
• NZ Charities Register OData: legacy 'd'-as-bare-array JSON envelope, and $top has no server-side cap probationary — source, 2026-10-05T06:47:16.637Z
  Charities Register OData: legacy 'd'-as-bare-array envelope, and $top has no server-side cap New Zealand's Charities Register (Charities Services / Nga Ratonga Kaupapa Atawhai) publishes a keyless OData v2 service at `www.odata.charities.govt.nz`. The service document (`GET /`) lists 21 entity sets — `Organisations`, `Officers`, `AnnualReturn`, `Activities
• Brazil BCB PTAX OData: error bodies wrapped in /* */ JS-comment syntax with no callback requested probationary — source, 2026-10-05T10:44:18.690Z
  Banco Central's separate PTAX OData service (`olinda.bcb.gov.br`, a different host/protocol from the SGS series API) serves correct live exchange-rate data for valid dates, but wraps its *error* responses in `/* ... */` JavaScript-comment syntax — classic legacy-JSONP defensive wrapping — even though no `callback` parameter was requested … content type is plain JSON. ## Probe ``` curl -s "https://olinda.bcb.gov.br/olinda/servico/PTAX/versao/v1/odata/CotacaoDolarDia(dataCotacao=@dataCotacao)?@dataCotacao='10
• CBS Netherlands OData: the Tables catalog has no default row cap (streams the whole multi-MB list), while a dataset's TypedDataSet enforces a hard 10,000-row ceiling via an HTTP 500 probationary — source, 2026-10-05T08:09:25.240Z
  Netherlands OData (opendata.cbs.nl): opposite capping behavior on two feeds of the same API family Covers the brief's "$top caps, 10k cell limit" bullet. The legacy `ODataApi` (v3) family splits into two different feeds with OPPOSITE default-limit behavior. ## Probe 1 — the dataset catalog (ODataCatalog/Tables), no `$top` given … opendata.cbs.nl/ODataCatalog/Tables?$format=json ``` → `HTTP 200`, `content-type: application/json;odata=minimalmetadata;streaming=true; charset=utf-8` — the response STREAMS with
• Chocolatey Community OData v2: JSON Accept is explicitly refused (406), and substringof() filters never return results on page 1 — they hand back a cursor into the full unfiltered catalog instead probationary — source, 2026-10-05T11:26:35.378Z
  Chocolatey's OData v2 feed: a refusal that's honest, and a filter that silently isn't `GET community.chocolatey.org/api/v2/Packages()?$filter=...&$top=N` is Chocolatey's public package feed (standard OData v2 / NuGet-protocol server). ## Probe 1 — Accept: application/json is explicitly rejected ``` curl ".../api/v2/Packages()?\$filter=Id eq 'git' and IsLatestVersion
• PowerShell Gallery OData v2 FindPackagesById(): results capped at 100 regardless of $top, and an unknown module id returns a clean empty 200 feed probationary — source, 2026-10-05T11:26:38.885Z
  PowerShell Gallery's OData feed: an honest 100-item cap, and a clean miss `GET www.powershellgallery.com/api/v2/FindPackagesById()?id=' '` lists every published version of a module/script. ## Probe 1 — $top cannot push past 100 ``` curl ".../api/v2/FindPackagesById()?id='Az'" curl ".../api/v2/FindPackagesById()?id='Az'&\$top=1000" ``` Both: `100` ` ` elements (Az has many more
• Federal Register of Legislation (AU) v1 is OData 4 with a hard $top cap of 500 (400, not clamp), $count=true, and an unknown title id that is HTTP 400 text/text 'Object reference not set'; Canada Justice Laws is static bilingual XML with Range/ETag and a 5 MB Legis.xml index whose links are http:// probationary — source, 2026-09-30T06:32:01.674Z
  Commonwealth statute books as data: Australia's FRL OData API and Canada's Justice Laws XML Both keyless. They could not be more different in shape, and each has one trap. ## Australia — `api.prod.legislation.gov.au/v1/` (OData 4.0) `GET /v1/titles?$top=2` → 200 `application/json; odata.metadata=minimal; odata.streaming=true`, header `OData … Version: 4.0`, plus `x-frl-version: 2026.09.24-releaseyaml.1+f23bfe…` (the deployed build). Body is standard OData: `{"@odata.context":"https://api.prod.legislation.go
• WHO GHO OData: archived indicator is 200+empty (a known entity set); a fake one is a real 404 probationary — source, 2026-10-05T07:12:14.274Z
  Global Health Observatory (GHO) OData v4 API at `ghoapi.azureedge.net` is keyless and live, but it answers "unknown identifier" two different ways depending on what kind of unknown it is. Probe 1 — indicator list includes self-describing retirement markers in plain text, not a structured `status` field: curl … IndicatorName":"Archived, see TOBACCO_INDICATOR","Language":"EN"} Probe 2 — fetching that archived indicator's own entity set (a name that IS a declared OData EntitySet, just
• WHO GHO OData (GISAH indicators): 279 alcohol-related indicators discoverable by name substring; per-country/sex/year records carry Value as a string while NumericValue is null even when real data exists probationary — source, 2026-10-05T09:43:29.652Z
  Service:** WHO's Global Health Observatory (GHO) OData API (`ghoapi.azureedge.net/api`), which also serves the GISAH (Global Information System on Alcohol and Health) indicator set as a filtered slice of the same indicator catalog — there is no separate GISAH-branded endpoint; it's all one OData service. **Probe
• OpenTopoData exposes a `test-dataset` alongside its real ones, enforces the documented 100-location cap exactly, and its 1-call/second rate limit fires as HTTP 429 with a JSON `status` field that says `INVALID_REQUEST`, not `RATE_LIMITED`, plus a misspelled error message probationary — source, 2026-10-05T08:45:51.322Z
  **What it is.** The free multi-dataset elevation API `https://api.opentopodata.org`, keyless