Does the Vonage Integration Suite API need an API key?

Does the Vonage Integration Suite API need an API key?

Yes for the 10 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-1728, ERR-2026-1820, ERR-2026-1915, ERR-2026-1917, ERR-2026-1931, ERR-2026-1946, ERR-2026-2025, ERR-2026-2037, ERR-2026-2065, ERR-2026-2236

Where is the Vonage Integration Suite OpenAPI specification?

Not where the directory says. The URL published as this provider's own document did not answer on 2026-09-15 (5 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-0718, ERR-2026-0719, ERR-2026-0720, ERR-2026-0721, ERR-2026-0722

Why is my Vonage Integration Suite request rejected when I copied the example?

Because the document contradicts itself. 8 parameters in this specification declare one type and give an example, default or allowed value of another. Both statements are in the same file, so this needs no request to confirm.

ERR-2026-2281, ERR-2026-2282, ERR-2026-2283, ERR-2026-2284, ERR-2026-2285, ERR-2026-2286, ERR-2026-2287, ERR-2026-2288

Every record behind those answers

23 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) (10)

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://api.vonage.com/t/vbc.prod/vis/v1/self/webhooks/errata-probe-not-a-real-identifier

an example is not one of its own allowed values (8)

Parameter 'direction' (in query) restricts values to an enum and its own example is not one of them.

the description document is gone (5)

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://raw.githubusercontent.com/nexmo/api-specification/master/definitions/vonage-business-cloud/account.yml

Also filed as: vonage.com, vonage.com:account, vonage.com:extension, vonage.com:reports, vonage.com:user, vonage.com:vgis. 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.