Where is the nexmo.com OpenAPI specification?

Where is the nexmo.com OpenAPI specification?

Not where the directory says. The URL published as this provider's own document did not answer on 2026-09-15 (20 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-0561, ERR-2026-0562, ERR-2026-0563, ERR-2026-0564, ERR-2026-0565, ERR-2026-0566, ERR-2026-0567, ERR-2026-0568, ERR-2026-0569, ERR-2026-0570, ERR-2026-0571, ERR-2026-0572

Every record behind those answers

20 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 (20)

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

ERR-2026-0561https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/account.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0562https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/application.yHTTP 404checked 2026-09-15, 2 times
ERR-2026-0563https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/application.vHTTP 404checked 2026-09-15, 2 times
ERR-2026-0564https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/audit.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0565https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/conversation.HTTP 404checked 2026-09-15, 2 times
ERR-2026-0566https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/conversation.HTTP 404checked 2026-09-15, 2 times
ERR-2026-0567https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/conversion.ymHTTP 404checked 2026-09-15, 2 times
ERR-2026-0568https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/dispatch.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0569https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/external-accoHTTP 404checked 2026-09-15, 2 times
ERR-2026-0570https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/media.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0571https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/messages-olymHTTP 404checked 2026-09-15, 2 times
ERR-2026-0572https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/number-insighHTTP 404checked 2026-09-15, 2 times
ERR-2026-0573https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/numbers.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0574https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/pricing.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0575https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/redact.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0576https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/reports.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0577https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/sms.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0578https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/subaccounts.yHTTP 404checked 2026-09-15, 2 times
ERR-2026-0579https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/verify.ymlHTTP 404checked 2026-09-15, 2 times
ERR-2026-0580https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/voice.ymlHTTP 404checked 2026-09-15, 2 times

Check it yourself:

curl -sS -o /dev/null -w '%{http_code}\n' https://raw.githubusercontent.com/nexmo/api-specification/master/definitions/account.yml

Also filed as: nexmo.com:account, nexmo.com:application, nexmo.com:application.v2, nexmo.com:audit, nexmo.com:conversation, nexmo.com:conversation.v2, nexmo.com:conversion, nexmo.com:dispatch. 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.