> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/user-api/resources/login-redirect.md). # Login redirect GET parameters that send a user straight to a chosen section of the login page, in a chosen language. A login redirect is a set of GET parameters on your login page URL. Link to it from your own website and a user lands on the section you chose, in the language you chose, instead of the default login form. {% hint style="info" %} This is the one thing in this section that is not an API call. Nothing is requested and nothing is returned: you build a URL, and the Navixy platform reads it when the user arrives. {% endhint %} ### Page section You can define the section which your users land by default with `partition` parameter: * `user`– user login page (used by default) * `demo` – access a chosen demo account * `register_fast` – quick registration form * `register_full` – full registration form * `password_remind` – password reminder ### Language Use `locale` parameter to define which language will be used: * `en_EN`– English * `es_ES` – Spanish * `ru_RU` – Russian * etc. If this parameter is omitted, the language which was set by default for your service will be used. ### Examples The next code will land user on login section with Spanish language: ``` http:///login/?partition=demo&locale=es_ES ``` The code below lands user on quick registration form with default language set by default: ``` http:///login/?partition=quick_register&locale=es_ES ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://navixy.com/docs/navixy-api/user-api/resources/login-redirect.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.