401 Access Denied when connecting to the web socket

euroq · December 11, 2025, 7:15am

I’ve been trying to connect to the websocket for the user-sync-request.

When connecting to either the demo or live wss://live.tradovateapi.com/v1/websocket I get a 401 Access Denied response from the server. This is on the actual authorize message that is sent after o so i can’t even get to the user sync request. I’m not using 2FA. I’m able to use all of the REST API just fine. I don’t have market data subscription, but I’m not connected to the md endpoint.

I am pretty sure I was able to do this in the past so I’m not sure what’s changed. Note that I have a primary account with plenty of money in it, but a secondary account that only has $800 so i wonder if that’s a problem.

This is an example of what I’m following:

github.com/tradovate/example-api-faq

example-code/user-sync-request/README.md

main

# User Sync Request

This is a working sample that allows a client to subscribe to user updates. To use this project, clone the repo and navigate to the containing folder using the command line. Be sure to navigate to this project's containing folder (`user-sync-request`). Then run this command:

```
yarn install
```

You can then run the application using this command:

```
yarn start
```

Be sure to fill out your credentials in the `data.js` file. Once the app is running, open your dev tools to see the websocket log its messages. If you were to have trades happening, you'd be able to see the updates for your positions and cashbalances coming in via this subscription. The initial response of this subscription is an object that contains all your current user data at the time of this subscription's start.

euroq · December 12, 2025, 12:06am

Don’t know if this matters or not, but I can’t even get the demo endpoint to work, let alone the live endpoint.

Johann_Birle · December 18, 2025, 12:34pm

sounds like rest auth is fine, but the websocket authorize step is failing.
not related to account balance or market data, especially since demo fails too.
usually this happens when the access token is missing, expired, or not passed correctly in the ws authorize message (or using the wrong token type).

Topic		Replies	Views
Issue with user/syncrequest WS endpoint - 401 error API Developers	3	459	June 8, 2022
401 Unauthorized Community Support	7	586	December 13, 2021
User/syncrequest WS request returns 401:Access is denied API Developers	2	358	March 29, 2022
Python WebSocket client doesn't work for API Developers	7	771	December 14, 2022
401 error when not using demo Community Support	6	284	March 8, 2022

401 Access Denied when connecting to the web socket

Related topics