just signed up and when i login it just cycles and goes back to the login screen. anyone else having this issue?
@Brandon1 Hello, first off welcome and apologies for a confusing first Alpaca experience. I sent you a direct message requesting the email address you used to sign up. I can check a few things with tha info.
I’m having this same issue, makes me a little worried to try to use this api.
@Aaron_Smith What type of issues are you having logging in? What are you trying to log into? The trading dashboard?
Alpaca – Crypto, Stock Trading API I just signed up and when I log in I just get redirected to the login page again no matter what I do. I tried resetting my password, which seemed to work, but still the redirect loop.
@Aaron_Smith I can’t replicate the issue but have asked the Tech UI Team to check what could be the issue. Apologies for the inconvenience.
Im having this same issue, any updates?
i’m having the same problem..
it redirects from login to alpaca.markets and then redirects back to login.. with an error.. which shows up for for a short time.. could not find it in the developer tools.. but starts with ‘something went wrong’ - i think
i also reset the password, same issue
@iwant_ubermind The Engineering Team is now able to reproduce this issue and is working on a fix. I’ll keep everyone posted. Again, apologies for the frustration.
Installing a ‘hot fix’ now. Should be back to normal soon.
Had a few curve balls getting this fixed, but should be good to go now. Again apologies for the inconvenience.
Yes, I am having the same issue. I just signed up and received a confirmation email.
I clicked on confirmation email and said it is invalid, but the upper right corner said it was already confirmed.
Then I logged in separately. It says sucessfully logged in in the upper right corner, but then shows the login page again.
It’s December and I’m having exactly the same problem as everybody else here who have been pointing out to this problem for months. Not a great first experience, I’ll look for another API provider.
@dccheung @mvell Are you still having issues? There was a scheduled maintenance on Saturday, December 13, 2025 from 9:00–10:00 am EST. That seems to be about the time of these login problems.
I’m looking into the issue now and trying to reproduce it. I’ll pass what I find on to the engineering team, and then post back here.
Apologies for the inconvenience.
I just created a new user account. When I log in it says that it was successful in the upper right corner, then I am immediately redirected to login again.
I can confirm I just signed up for the Alpaca account, was sent the confirmation email, see confirmed and then get caught in the sign in loop, without being able to log in.
Same issue here - just signed up, stuck in a login loop. It appears to be an issue with the email confirmation module lagging in whitelisting our accounts.
Everyone, Alpaca is aware of this issue and have been able to reproduce it. A fix is in the works and should be deployed very soon. Apologies for all of the inconvenience.
Dan,
So how can I get help with this issue? I see the thread got closed and I was redirected to a website that show no connection to Alpaca (Defi Protocol). I have one usable account still working for my bots, but these new accounts continue to show a insuffiencent cash attached to both new accounts with different emails.
Server-Side Caching and Session Corruption
I have been running my issues through Ai to see if I could fix the issues, but it seems its not on my end… here is the output. Is there any fix for this as I have created 2 new accounts with different emails and still get the same fatal error after I generate keys for the new paper accounts?
The issue you are facing is a known, recurring, and complex server-side problem with Alpaca’s paper trading environment. The core issue you are experiencing is a combination of the following known behaviors:
”FATAL: Insufficient Cash ($-7713.80). Please reset/fund account”
-
“Reset” Creates a New Account, Doesn’t Delete the Old One: When you “reset” a paper account in the dashboard, it creates a new account with new keys and a fresh balance. The previous account remains “inactive” but is not immediately deleted.
-
Old Keys/Session Data Persist: Because the old account remains inactive, old API keys and session tokens can still return data from the old account, leading to confusion. This is precisely why your commands kept returning the negative balance from the indebted account.
-
Client/Server Mismatch: The API client (our Python bot) tries to fetch data, but the server, due to a caching error, associates your user credentials with an old, indebted session ID (
782e0ffa...) rather than the active, newly funded account (PA323HEJ...)