Based on the knowledge sources provided, there is some information about potential changes to response codes in Ory, particularly around account linking and authentication flows. From the GitHub issue discussions, it appears that Ory is considering changing some HTTP status codes to be more semantically correct. Currently, there's an open issue (#4052) discussing how requesting a login code returns HTTP 400, which some users feel is not the most appropriate status code for this scenario. The Ory team is considering replacing 400 Bad Request responses with more specific codes like: - 422 Unprocessable Entity for validation errors - 202 Accepted for interrupted flows (like sending activation emails) - 401 Unauthorized for multi-step authentication processes As mentioned by an Ory team member in [Github Issue #4052](https://github.com/ory/kratos/issues/4052): > "We have opportunity to improve status code for certain endpoints (but need to do it without breaking changes to existing clients which will be very challenging) and their responses. Sending 200 OK for anything where the request is not successful and finished is not in the mix." However, they also note that such changes would likely not happen before 2026 due to the complexity of implementing these changes without breaking existing clients. Regarding account linking specifically, there are some discussions about improving the user experience, especially in cases where users need to link accounts between different providers or when using passwordless authentication methods. If you're looking for more specific information about an upcoming change to account linking response codes, the knowledge sources don't provide definitive details about an imminent change that has been officially announced.