@admin Hello Team,

My Angel One Client ID is AACA740024, but in the SmartAPI portal under My Profile, the “AngelOne Client ID” field shows N/A.

Because of this, SmartAPI is unable to authenticate my WebSocket session.
I can generate a session token using API Key + PIN + TOTP, but when WebSocketV2 connects, the backend rejects the connection because the client_code parameter must match the registered Angel One Client ID, and SmartAPI does not have it stored.

This leads to repeated WebSocket failures:

WS error: Connection closed
Connection closed due to max retry attempts reached

SmartAPI requires the Client ID to be mapped to my SmartAPI app for the following:

Real-time WebSocket authentication

Subscribing to tokens on NSE

Placing REAL orders via SmartConnect

Fetching holdings, orderbook, positions, and profile

Generating feedToken linked to the correct client_code

Without the Client ID recorded in my SmartAPI profile, SmartWebSocketV2 cannot authorize, even though the login token is valid.

Please update my SmartAPI profile to reflect:

Angel One Client ID: AACA740024

This is required for API authentication and for my trading application to function.

Thank you.

@admin[link text](link url)

I am writing to request linking my AngelOne trading account to the SmartAPI developer portal. Currently, my SmartAPI profile shows Client ID as N/A, which prevents me from using the API for automated trading. Here are my account details for verification

please migrate SRYB1020