Create an account and sign in

Choose the identity you will keep

Your OrderMap account owns your layouts, watchlists, alerts, tickets and developer projects. Start with the email address you intend to use consistently. A second email can lead to a separate account, even when both addresses belong to you. Creating a developer key, opening a payment page or receiving a verification email does not complete account registration. The normal signup flow first proves control of the email address, then collects the required profile information before granting a normal application session.

Complete email verification

Choose Create an account on the sign-in screen and enter your email carefully. Follow the verification message using the browser where you started signup when the flow asks for that browser. Verification links are single-use and time-limited; repeatedly reopening an older message can produce an expired or already-used result. Keep the original signup tab available until the next page appears. A successful email request means the request was accepted, while the message's arrival and the completion of verification are separate outcomes.

1. Choose Create an account and submit the intended address.
2. Check the inbox and spam folder for the current verification message.
3. Open the current link and follow the resulting registration or waitlist instructions.

Understand the registration waitlist

New registrations can enter a verified waitlist before an account is created. The waiting page says, “We will let you know once you're off the waitlist.” This is a saved admission position rather than a signed-in workspace. Waiting does not create a billing trial or grant market access. An admission email tells you registration is open for that address; it is not an authentication credential. If your original proof has expired by then, complete fresh email verification or the appropriate Google flow to continue onboarding.

Finish the required profile

After admission, provide the required first name, last name and unique username. A username collision needs a different available value; it does not mean email verification failed. Complete the profile and onboarding steps presented by the application, then wait for the workspace to open. The account is created only when the required flow commits successfully. An unfinished onboarding page cannot access ordinary account APIs simply because it has a temporary registration cookie. If a save is unavailable, retain the visible error and retry the current step when service resumes.

Use a method linked to this account

Email/password, Google and passkeys depend on server availability and the methods already established for your account. A passkey must have completed enrollment before it can sign you in. Google Connected in Security refers to a linked Google identity; a similar-looking email alone does not prove that identity was linked. Once signed in, open Settings → Security to inspect the methods actually available. Select a familiar method when diagnosing access, so changing both the account address and the method does not obscure which identity is being used.

Check the result after sign-in

A normal sign-in should return you to the terminal with the expected account identity and saved resources. Open Settings → Account and verify the email before deciding a layout or subscription has disappeared. An explicit Preview or development account has separate fixture identity and billing behavior; it is not evidence that your regular account's information was erased. Signing out and choosing the intended account is appropriate when the displayed identity is wrong. Support access belongs to the authenticated account and does not require buying a market-data plan.

Resolve verification and sign-in failures

For an expired link, request a fresh verification flow instead of forwarding the old credential between browsers. For a password failure, use the password-reset flow rather than guessing repeatedly. A Google-not-enabled message needs an available alternative method or a configuration investigation. If registration remains blocked, report the sign-in method, visible waiting or onboarding step, approximate time, browser and safe error text. Include the account address through the private ticket only when needed. Never attach the verification link, password, Google authorization code, session cookie or complete developer key.