Does the Medium API need an API key?

Does the Medium API need an API key?

It depends on the operation. Of those checked on 2026-09-15, 7 refused an anonymous request and 5 answered one. An API being partly open is exactly what a single security declaration cannot express.

ERR-2026-1740, ERR-2026-1802, ERR-2026-1905, ERR-2026-1927, ERR-2026-2006, ERR-2026-2050, ERR-2026-2084, ERR-2026-1759, ERR-2026-1795, ERR-2026-1818, ERR-2026-2074, ERR-2026-2223

Where is the Medium OpenAPI specification?

Not where the directory says. The URL published as this provider's own document did not answer on 2026-09-15 (2 entries). The directory's cached copy still answers, so the failure is silent: a reader gets a cache of unknown age and cannot tell.

ERR-2026-0326, ERR-2026-0631

Why can't I reach the Medium API?

Its declared address answered neither a request nor a TLS handshake on 2026-09-15, across 1 case. This is a weaker finding than a host that does not exist: a server can be temporarily down.

ERR-2026-0630

Every record behind those answers

15 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 121 have been across the whole registry.

credentials are required (observed) (7)

The document establishes no authentication requirement for this operation; an anonymous request is refused with 401. The requirement is now observed rather than unknown.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://medium2.p.rapidapi.com/search/articles?query=errata-probe-not-a-real-identifier

usable with no account (observed) (5)

An anonymous request is answered with a machine-readable response. The operation is reachable with no account. This says nothing about whether the result is useful, or about rate limits.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://api.corrently.io/v2.0/tariff/slph0

the description document is gone (2)

The document APIs.guru names as this provider's own origin returns HTTP 404.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://corrently.io/dist.yaml

server error (1)

The declared provider origin answered with a server error.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://corrently.io/attachments/4

Withdrawn (23)

Our own check stopped supporting these claims — including claims that were wrong the day they were written.

Also filed as: Corrently.io, Football Prediction API, corrently.io, rapidapi.com, rapidapi.com:ecowetter, rapidapi.com:language-identification. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.

If a record here is wrong

Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 121 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.

What this page does not tell you

This is not a clean bill of health for anything not listed. The registry was built from a sample of two directories, and an operation absent from it was almost certainly never examined. Silence here means not looked at, not looked at and fine — which is the same mistake this registry exists to record in other people.

What this is

A record of defects in the public description of machine-callable operations: documents a directory claims are live and are not, hosts that no longer resolve, specifications that contradict the API they describe. It is not a ranking, not a review, and not a judgement about the service. No credential is ever sent to anything listed here.

The whole registry, machine-readable: errata.json. Index of subjects: index.html.

Built from registry errata-2026-09-10@b7cb54d3a847. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.