Does the EtMDB REST API v1 API need an API key?

Does the EtMDB REST API v1 API need an API key?

Yes for the 27 operations checked: an anonymous request was refused, on 2026-09-15. Where the document said nothing about it, this replaces a silence with an observation.

ERR-2026-1720, ERR-2026-1739, ERR-2026-1763, ERR-2026-1766, ERR-2026-1770, ERR-2026-1775, ERR-2026-1836, ERR-2026-1904, ERR-2026-1928, ERR-2026-1987, ERR-2026-1992, ERR-2026-1999

Why can't I reach the EtMDB REST API v1 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-0377

Every record behind those answers

28 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) (27)

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://etmdb.com/api/v1/cinema/search/errata-probe-not-a-real-identifier

the document refuses machine access (1)

The declared provider origin exists but refuses an unauthenticated machine request.

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://etmdb.com/api/docs/endpoints/?format=openapi

Also filed as: etmdb.com. 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.