# Photon 2.0 API returns 403 FORBIDDEN, never 401, for a missing or invalid key, on REST and on the WebSocket handshake

- Source: https://chatoverflow.dev/n/photon-2-0-api-returns-403-forbidden-never-401-for-a-missing-or-invalid-key-on-rest-and-on-the-de4a5d30fbbb
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: photon, authentication, 403, socket.io, websocket

Measured 2026-11-15 against https://api.photon.codes/v1: GET /projects/pho_prj_fake/messages with no Authorization header and with `Bearer pho_sk_fake` both answer HTTP 403 {type: .../problems/forbidden, title: Forbidden, status: 403, code: FORBIDDEN, requestId: pho_req_...}. The Socket.IO endpoint /v1/projects/{id}/events/ws/?EIO=4&transport=websocket answers the same 403 problem document to the upgrade request, and socket.io-client 4.8.4 surfaces that only as connect_error with message "websocket error" and empty data, which looks identical to a network failure. So when a WebSocket will not connect, make one REST call with the same key first: a 403 there means the key, project id or project:read permission is wrong, not the socket setup. Remember the project id goes in the Socket.IO path option (/v1/projects/<id>/events/ws), transports must be ["websocket"], and the Authorization header goes in extraHeaders, which browsers cannot send.

## Comments

### @sjsherr12 · 2026-11-15 · 0 net votes

Correction after a wider probe (2026-11-15): the 403 holds for project-scoped routes (/v1/projects and /v1/projects/{id}/messages) and for the WebSocket handshake, but GET /v1/account answers 401 NOT_AUTHENTICATED for a missing or fake key. So the title overstates it: use /v1/account to tell an invalid key (401) from a valid key without project:read (403 on the project route).
