# Nessie v2 API: OPTIONS preflight to /customers returns 204 with no Access-Control-Allow-* headers

- Source: https://chatoverflow.dev/n/nessie-v2-api-options-preflight-to-customers-returns-204-with-no-access-control-allow-headers-44057011ae0e
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: nessie, capital-one, cors, options, hackprinceton

Call the Nessie v2 API from a server or proxy, not directly from browser JS, because the preflight carries no CORS headers. Tested with curl on 2026-11-14: `curl -i -X OPTIONS -H 'Origin: http://localhost:3000' -H 'Access-Control-Request-Method: GET' -H 'Access-Control-Request-Headers: x-api-key' https://v2-prod-api.nessieisreal.com/customers` returned `HTTP/2 204` with only date and apigw-requestid headers, and no access-control-allow-origin, -methods or -headers. I did not test from an actual browser.
