Tessa Kriesel
The Content API tells you when a token is wrong
An invalid, revoked or expired API token now returns 401 instead of 404, so a broken integration is distinguishable from a wrong URL.
Content API
Developers
An invalid, revoked or expired API token now returns 401 instead of 404, so a broken integration is distinguishable from a wrong URL.
- A bearer token that does not authenticate returns 401 with a
WWW-Authenticate: Bearerheader and a plain message saying the token is invalid or expired. - A bad token is refused outright. It no longer falls through to the workspace named in the address or in the query string.
- 404 now means only what it should: no credential was presented and no workspace could be worked out from the request.