Not where the directory says. The URL published as this provider's own document did not answer on 2026-09-15 (12 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-0458, ERR-2026-0459, ERR-2026-0460, ERR-2026-0461, ERR-2026-0462, ERR-2026-0463, ERR-2026-0464, ERR-2026-0465, ERR-2026-0466, ERR-2026-0467, ERR-2026-0468, ERR-2026-0469
12 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 document APIs.guru names as this provider's own origin returns HTTP 404.
ERR-2026-0458 | https://api.hubspot.com/api-catalog-public/v1/apis/events/v3/send | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0459 | https://api.hubspot.com/api-catalog-public/v1/apis/oauth/v1 | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0460 | https://api.hubspot.com/api-catalog-public/v1/apis/automation/v4/actions | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0461 | https://api.hubspot.com/api-catalog-public/v1/apis/business-units/v3 | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0462 | https://api.hubspot.com/api-catalog-public/v1/apis/cms/v3/domains | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0463 | https://api.hubspot.com/api-catalog-public/v1/apis/communication-preferences/v3 | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0464 | https://api.hubspot.com/api-catalog-public/v1/apis/conversations/v3/visitor-identification | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0465 | https://api.hubspot.com/api-catalog-public/v1/apis/extensions/sales-objects/v1/object-type | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0466 | https://api.hubspot.com/api-catalog-public/v1/apis/events/v3/events | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0467 | https://api.hubspot.com/api-catalog-public/v1/apis/files/v3/files | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0468 | https://api.hubspot.com/api-catalog-public/v1/apis/marketing/v3/marketing-events-beta | HTTP 404 | checked 2026-09-15, 2 times |
ERR-2026-0469 | https://api.hubspot.com/api-catalog-public/v1/apis/webhooks/v3 | HTTP 404 | checked 2026-09-15, 2 times |
Check it yourself:
curl -sS -o /dev/null -w '%{http_code}\n' https://api.hubspot.com/api-catalog-public/v1/apis/events/v3/send
Also filed as: hubapi.com:analytics, hubapi.com:auth, hubapi.com:automation, hubapi.com:business units, hubapi.com:cms, hubapi.com:communication-preferences, hubapi.com:conversations, hubapi.com:crm. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.
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.
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.
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.