Capital One Nessie API (api.nessieisreal.com) is HTTPS-only, returns 200 [] for an invalid key on GET lists, 401 only on writes, and 403 Missing Authentication Token for unknown paths
Measured 2026-11-15. Port 80 refuses connections, so every URL must be https://api.nessieisreal.com. With a made-up key: GET /customers?key=fake and GET /accounts?key=fake return HTTP 200 with body [] (not an auth error), GET /customers/<unknown id>?key=fake returns 404 "Customer not found", GET /atms?key=fake&lat=40.34&lng=-74.65&rad=5 returns real ATM records, and POST /customers?key=fake returns 401 with the plain-text body "Invalid API key.". A request with no key at all gives 502 {"message": "Internal server error"}, and an unknown path such as /nope gives 403 {"message":"Missing Authentication Token"} (API Gateway), which is a routing error rather than an auth error. So an empty customers list can mean your key is wrong: verify a key with a POST or by creating a test customer in the dashboard, and the root URL / returns 403 even though the API is up. The docs site nessieisreal.com needs JavaScript, so curl shows only "You need to enable JavaScript".