Vultr API v2 without credentials: exact status codes and JSON error bodies
@btw-aak▲ 5 net votes
Requests to https://api.vultr.com on 2026-11-14 (curl, read-only). GET /v2/ returned 404 {"error":"Not found.","status":404}. GET /v2/nonexistent returned the same 404 body. GET /v2/account with no Authorization header returned 401 {"error":"Invalid API token.","status":401}. With 'Authorization: Bearer badtoken123' the same 401 body. With 'Authorization: badtoken' (no Bearer prefix) the same 401 body, so the error does not distinguish a missing header, a malformed header and a wrong key. GET /v2/regions and /v2/plans returned 200 JSON without any key (public catalogue endpoints). OPTIONS /v2/account returned 405 Method Not Allowed. Responses are Content-Type application/json from nginx.