Can multiple mStock accounts share one static IP?

We strongly recommend one IP per account. Broker risk systems correlate accounts by origin IP; sharing an address across clients can link unrelated accounts and multiply the blast radius of any flag.

mStock (Mirae Asset) Trading API with Static IP: Setup Guide

Configure the mStock by Mirae Asset Trading API with a dedicated static Indian IP — whitelisting steps, proxy configuration and session stability tips.

Why mStock traders buy static IPs

mStock by Mirae Asset has become popular with cost-sensitive algo traders thanks to its Type A/B/C API plans and zero-brokerage structure. Like every serious Indian broker API, it expects consistent, attributable request origins — and many resellers and trading desks provision one dedicated IP per mStock client as standard practice.

Step 1 — Get your dedicated IP

Allocate an IPv4 static IP at algo-ip.in (₹200/month retail; agencies get wholesale rates and can provision per-client IPs through our Agency API). You receive the IP, proxy host, HTTP port 443, SOCKS5 port 1080, and credentials.

Step 2 — Register the IP with mStock

In the mStock developer/API section, register your API app and provide your static IP where origin/server IP is requested. Keep a note of the exact address — the whitelist match is exact.

Step 3 — Route your client through the proxy

Step 4 — Session stability tips

Generate your daily session token after the IP check passes, never before.
Keep WebSocket market-data connections on the same proxy as order calls.
If you run multiple mStock client accounts (family/agency), use one dedicated IP per account — never share an address across accounts.

For agencies and resellers

Algo-IP's Agency API lets platforms provision a dedicated static IP per end-client programmatically: POST /api/v1/agency/allocations with the client label, get back IP + credentials in one call, at wholesale pricing. Each allocation is whitelist-ready for mStock out of the box.