Two of my own accounts, one server: cannot create a second app — static IP already associated


  • I trade two of my OWN Angel accounts (not clients' accounts, no algo service,
    no third parties) from a single server with one static IP.

    Setup:

    • Account A: client code K76*** — SmartAPI app created, static IP 195.35.45.xxx
    • Account B: client code AACJ39**** — no app yet
    • Both traded from the same server, same static IP

    Problem:
    Creating a SmartAPI app for Account B is rejected with
    "static IP is already associated with another app"
    — on BOTH the Primary Static IP and Secondary Static IP fields.

    I then tried using Account A's API key for Account B. What I observed:

    • loginByPassword for Account B with Account A's key SUCCEEDS and returns a
      valid jwtToken, refreshToken and feedToken
    • but every subsequent call with that token fails with:
      {"success":false,"message":"Invalid App","errorCode":"AB1034"}
    • quote, getPosition, placeOrder — all AB1034

    So one API key clearly cannot be used for a second client code, and one static
    IP cannot hold a second app.

    My questions:

    1. What is the correct, supported setup for trading two of my own accounts from
      one server? Is a second static IP on the same server the intended answer, or
      can two apps be mapped to one static IP for the same beneficial owner?

    2. If two of my own accounts can share one static IP, what is the procedure?
      (written request, 2FA, documents — please specify)

    3. Why does loginByPassword succeed when the API key is not valid for that
      client? Returning a working token and then failing every call with AB1034 is
      very misleading — could login reject the mismatch up front instead?

    Happy to share the full client codes and IP privately if needed.
    Thank you.