thankful-shoe-14315
02/13/2026, 4:34 PMToSession (GET /sessions/whoami) endpoint via the Go SDK (github.com/ory/client-go) are failing with "undefined response type". This error originates from the SDK's response decoder, which expects a Content-Type matching application/json or application/xml. When the Content-Type doesn't match, the SDK can't parse the response and throws this error.
What we believe is happening: Something changed on the Ory Network side that altered the Content-Type header (or other response characteristics) returned by the /sessions/whoami endpoint. This is breaking the SDK's response parsing for both success (200) and error (401) responses.
What we've ruled out:
Not an expired session issue — happens on brand new sessions in incognito
• Not an SDK version issue — happening on both v1.22.16 and v1.22.23 simultaneously
• Not a code change on our side — prod (unchanged code) and dev broke at the same time
We're deploying additional debug logging to capture the full response details (status code, headers, body, Content-Type) and can share those shortly. In the meantime, can you check if there were any infrastructure or API changes around that time that could have affected response headers on the /sessions/whoami endpoint?thankful-shoe-14315
02/13/2026, 4:38 PMbland-eye-99092
02/13/2026, 4:40 PMbillions-minister-2901
02/13/2026, 6:41 PMbillions-minister-2901
02/13/2026, 6:44 PMbillions-minister-2901
02/13/2026, 7:38 PMbillions-minister-2901
02/13/2026, 8:23 PMthankful-shoe-14315
02/13/2026, 8:24 PM/sessions/whoami have been succeeding.billions-minister-2901
02/13/2026, 8:28 PMlemon-painter-27431
02/13/2026, 8:38 PMbland-eye-99092
02/13/2026, 9:01 PM/sessions/whoami endpoint and is caused by some internal routing issues. There should be no pagination involved here, so from your description this issue seems like something else. Could you raise this issue via console.ory.sh/support?lemon-painter-27431
02/13/2026, 9:59 PM