Is the Gateway API still reachable?

Is the Gateway API still reachable?

No, not at the address its own documentation gives. The host declared as its server did not resolve in DNS on 2026-09-15, across 3 indexed operations. A document can look current and still name a host that no longer exists — nothing looks wrong until the call.

ERR-2026-1863, ERR-2026-1892, ERR-2026-1872

Where is the Gateway OpenAPI specification?

Not where the directory says. The URL published as this provider's own document did not answer on 2026-09-15 (188 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-0025, ERR-2026-0026, ERR-2026-0027, ERR-2026-0028, ERR-2026-0029, ERR-2026-0030, ERR-2026-0031, ERR-2026-0032, ERR-2026-0033, ERR-2026-0034, ERR-2026-0035, ERR-2026-0036

Every record behind those answers

194 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.

the description document is gone (188)

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://apisetu.gov.in/api_specification_v8/aaharjh.yaml

… and 128 more, in the machine-readable registry.

timeout (2)

The host declared as this operation's server did not answer a TLS handshake.

Check it yourself:

dig +short healthidsbx.ndhm.gov.in

unreachable (1)

The host declared as this operation's server resolves but refuses a TLS connection.

Check it yourself:

dig +short dev.ndhm.gov.in

the declared server is a sandbox, and it is gone (1)

The host declared as this operation's server is a test or sandbox host, and it no longer resolves. A caller reaching for it gets nothing, and it would not have been production anyway.

Check it yourself:

dig +short betaapi.digitallocker.gov.in

the declared server domain looks like a typo (1)

The host declared as this operation's server contains what appears to be a typographic error in its domain.

Check it yourself:

dig +short cowin.gov.cin

the declared server host was never real (1)

The host declared as this operation's server is a placeholder or a private name that was never publicly resolvable.

Check it yourself:

dig +short your-hrp-server.com

Also filed as: Authorized Partner API Specification, Co-WIN Certificate API, Health ID Service, Health Repository Provider Specifications for HIP, apisetu.gov.in, apisetu.gov.in:aaharjh, apisetu.gov.in:acko, apisetu.gov.in:agtripura. 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.