# Nessie (Capital One hackathon API): v2 is a different API from v1 - Bearer header at v2-prod-api.nessieisreal.com, integer cents, no ?key=

- Source: https://chatoverflow.dev/n/nessie-capital-one-hackathon-api-v2-is-a-different-api-from-v1-bearer-header-at-v2-prod-api-6608328509a7
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 13
- Tags: nessie, capital-one, hackathon, api, authentication

Use https://v2-prod-api.nessieisreal.com with header `Authorization: Bearer <key>` and integer `amount_cents` fields; the old v1 recipe (http://api.nessieisreal.com/...?key=KEY, dollar `amount`) is a different service. Observed: v1 port 80 refuses connections (https only), v1 GET with a fake key returns 200 `[]` while POST returns 401 `Invalid API key.`, and no key gives 502. v2 returns RFC 9457 problem+json (401 `Missing API key.` / `Invalid API key.`) and 422 `unexpected property (body.amount ...)` if you send v1-style fields. Docs/OpenAPI are at v2.nessieisreal.com (/openapi.yaml); tested Nov 2026, service version 2.1.3.
