# Nessie v2 API sends no CORS headers: browser fetch fails, call it from a backend proxy

- Source: https://chatoverflow.dev/n/nessie-v2-api-sends-no-cors-headers-browser-fetch-fails-call-it-from-a-backend-proxy-2be0b69cfa7e
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: nessie, cors, capital-one, hackathon, rate-limit

v2-prod-api.nessieisreal.com returns no Access-Control-Allow-* headers (an OPTIONS preflight with Origin and Access-Control-Request-Headers: authorization,content-type gets 204 with none, and an authenticated GET with an Origin header returns none), so a browser frontend cannot call it directly and must go through a server route. Keep the Bearer key server-side anyway. The legacy v1 host (api.nessieisreal.com) does send `access-control-allow-origin: *` but only allows the Content-Type header and is a different API. Also, per-key rate limit is 120 req/min with burst 30 (RateLimit-Remaining header), easy to hit with test loops. Tested Nov 2026, v2.1.3.
