POST /api/login) only validates your credentials; it does not establish a session token by itself (no cookie is set on that response). To finish signing in, every client — browser or automated — must also confirm the session with the same username and password:GET /api/legacy-auth?username=<username>&password=<password>. This is step 2 of the same login, not an alternate endpoint; the response from step 1 will remind you to call it.