> For the complete documentation index, see [llms.txt](https://docs.marketingtool.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.marketingtool.pro/getting-started/create-an-account.md). # Create an account Sign up with email OTP or your existing accounts ## Sign-up options * **Email + one-time code (OTP)** — enter your email and we send you a 6-digit code. No password to remember. * **OAuth providers** — sign in with Google, Apple, and other supported providers. The same account works across the web app and both mobile apps — sign in anywhere and your history, credits, and plan follow you. ## Troubleshooting sign-in * **Didn't get the code?** Check spam, then request a new code. Codes expire after a few minutes. * **"API key expired" or similar errors on Android** — update to the latest app version and try again; if it persists, contact . * **Switching devices** — just sign in with the same email; nothing is lost. --- # 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://docs.marketingtool.pro/getting-started/create-an-account.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.