TWM Wiki

Description

Connections

Setting up a Connection


Please see video for an online example.




In order to download market data and/or trade user needs to configure a connection. Please proceed to Admin Panel -> Connections -> Configure to set up a new connection.


Image



Existing connections will appear in the drop down menu demonstrated in the picture above after they have been set up. To set up a connection proceed with choosing the configure option.

TWM is a multi connection platform and users can have numerous connections running simultaneously allowing data and trading from several exchanges. In order to connect to an existing connection use the toggle to the right hand side of the connection name right inside the menu.

After you are successfully connected to a provider a connection name will appear in the TWM admin panel bottom toolbar and a success message wıll print in the log tab of the admin panel.


Image


The connection configuration window will have available connections listed at the top. Each connection can only be added once by double clicking on it or by pressing the plus button which will move the connection from the top list to the bottom list to be available for further configuration. Please see individual connection instructions for further information on particular connection configuration requirements.


Image





Binance

If you want to place trades on Binance you will need to generate two types of keys on Binance, HMAC and ED25519. TWM uses HMAC for futures market websocket connection and all rest requests and uses ED25519 for spot websocket connection. If you just want to get data and/or trade using the local simulator just leave the fields API Key, API Secret, Websocket API Key and Webscoket Private Key blank. Below is a detailed walthorugh of the process.

  1. Login to your Bnance account
  2. Go to Account -> API Management
  3. Click Create API
  4. Click on Self-Generated
  5. After this you will get a window where you need to insert a public key
  6. In order to get the public key go here https://github.com/binance/asymmetric-key-generator/releases
  7. Download AsymmetricKeyGenerator-setup-v1.0.0.exe and AsymmetricKeyGenerator-setup-v1.0.0.exe.CHECKSUM
  8. Run assymetric key generator
Image
  1. Choose Ed25519 and click generate pair.
  2. Copy the public key and paste into the Binance prompt box where it asked you for the public key (with begin and end parts)
  3. The private key needs to be inserted into the Websocket Private Key field in TWM Binance connection configurator (without the begin and end parts, just the key part)
  4. Once created copy the API key to TWM Websocket API Key field
  5. Make sure you set appropriate permissions, below is an example of permisions required to make trades
Image
  1. After ths step you should have two fields left to fill in inside the Binance TWM connection configurator API Key and API Secret, this is for the next key
  2. Click Create API again
  3. This time choose System generated
  4. Create the key with identical permission and copy the API Key and API Secret to appropriate fields in TWM, note that secret will be only shown once on Binance and you will have to recreate if you loose it

It is highly recomended to restrict access to your trusted IP. You can see what IP you are using here https://whatismyipaddress.com/. Make sure you are not using dynamic IP that can change a few times even during a single day.

If you have set up a conection and after sometime you are not able to log in for some reason, please go to the above mentioned address and re-identify your IP to check whether it has changed or not. If it has changed, it means you have a dynamic IP and you might need to update it within the exchange restrictions regularly.

Please note that some old Binance accounts that have been set up prior futures have been introduced into Binance might by default require users to set up an IP filter in order to trade futures.


Please note that by default some Binance accounts do not have their Futures accounts enabled. In that case connection will fail even if your API keys are set up correctly. Please address this link to set up your futures account correctly https://www.binance.com/en/support/faq/detail/360033772992.


Bybit




For market data API key and secret is not required however for placing orders and reading account information API key and secret is compulsory. If you only want to get market data you do not need a Bybit account. Just set up a connection without any keys.

In order to set up an API key you will need to log into your account and go to https://www.bybit.com/app/user/api-management which is located under Account -> API. Please make sure your Bybit account is configured to use Unified Trading Account!!!. Bybit classic account is not supported.

If your Bybit account is not UTA (Unified Trading Account), you will usually see Spot and Derivates separately listed in your Dashboard. After you upgrade they will be merged to a single UTA (Unified Trading Account). On information about how to upgrade to UTA please contact Bybit support. Usually it is a very simple process and takes 2 minutes after you click a respective pop up button Upgrade to UTA somewhere on Bybit interface.

Image


Make sure you have set up appropriate permissions for spot and/or futures trading as shown in the illustration above. Also make sure you have selected Read and Write permissions as shown above as we need to post orders to the exchange in order to trade from within the TWM. Copy the provided API and Secret keys into TWM Bybit connection set up parameters.

It is highly recomended to restrict access to your trusted IP. You can see what you IP is here https://whatismyipaddress.com/. Make sure you are not using dynamic IP that can change a few times even during one day.


Image


You do need to give access to assets part of the API as shown above if you want to see your assets tab in TWM with remaining spot positions that you hold.


Cryptocom

TWM currently supports only SPOT symbols for crypto.com connection. In order to get public data, historical, order book and live streams you don't need to fill in any credentials such API key and secret. However, if you would like to trade and get updates on user data you will need to create an API key inside your crypto.com account. Please login and proceed to api management. This can be achieved by clicking on your account avatar in the right top most corner, then manage account option in the drop down menu and finally by choosing the api management tab.


Image


Click on create new api key and proceed with appropriate permissions in the modal window. Make sure to check can read and enable trading options. Also, you must whitelist you IP. After creation make sure to copu your API key and secret to appropriate fields inside you TWM crypto.com connection configuration.

Image



Important Information

  1. Please make sure that a chosen connection is available in your specific region or use a VPN if needed.
  2. When copying API keys and secrets make sure you do not copy any white space.
  3. TWM will attempt to download all available data the first time you ask for data no matter what period you ask for, please allow this first download to execute untill end.
  4. Upon creating the keys the system might ask you whether you would like system generated API keys or self generated API keys. It does not matter for TWM which ones you choose. You can read more about what the difference between them is upon creation in the information provided by the exchange.
  5. Upon API key creation do not forget to create a name for it, it does not matter for TWM what name you create, just a name that you can identify for your personal use. Some exchanges might not allow you to proceed without the name, watch out for hints from the exchange UI that can help you identify what is required to be filled in.
  6. If you are not able to connect for some reason after you have been using a connection for a while and you are sure its not an IP filter, check the expiry dates on your exchange API configuration. Some exchanges provide API keys that expire after a certain period.
  7. Remember that if you set up a connection without an api key and secret it will still connect to public data but you won't be able to trade or get your account balance. On the other hand if you do set up a connection and fill out the API keys and make a mistake in them or your API key expires, then you will not be able to connect and will get a generic "Check your credentials" warning message.


This website uses cookies to enhance your browsing experience. By continuing to use our website, you agree to our Privacy Policy

Necessary cookies help make a website usable by enabling basic functions such as page navigation and access to protected areas of the site.

  • Necessary cookies

    .AspNet.Consent

    Indicates whether the user has consented to the use of necessary cookies.

    Maximum storage duration: 1 Year | Type:Necessary cookies
    .AspNetCore.Antiforgery

    Used to prevent CSRF attacks and protect user data.

    Maximum storage duration: Session | Type: Necessary cookies
    .AspNetCore.Cookies

    Used to manage authentication information and the user's session.

    Maximum storage duration: 1 Year | Type: Necessary cookies
    .AspNetCore.Culture

    Used to store user's language preferences.

    Maximum storage duration: 1 Year | Type: Necessary cookies
    __Secure-OSID

    Security cookie set by Google to authenticate users and prevent fraudulent use of login credentials.


    Maximum storage duration: 6 Months | Type: Necessary cookies
    __Host-3PLSID

    Ensures you stay connected to your Google accounts across various services.

    Maximum storage duration: 2 Years | Type: Necessary cookies
    AEC

    Used to verify your Google account and ensure that requests in sessions come from you.

    Maximum storage duration: 6 Months | Type: Necessary cookies
    HSID

    Security cookie used by Google to authenticate users and prevent fraudulent use of login credentials, protecting user data.

    Maximum storage duration: 2 Years | Type: Necessary cookies
    SEARCH_SAMESITE

    This cookie prevents the browser from sending the cookie along with cross-site requests, helping to mitigate the risk of cross-origin information leakage.

    Maximum storage duration: 6 Months | Type: Necessary cookies
    SID

    Important for Google's security and to ensure that Google can authenticate the account and block fraudulent access attempts.

    Maximum storage duration: 2 Years | Type: Necessary cookies
    SIDCC

    Security cookie to protect user data from unauthorized access.

    Maximum storage duration: 1 Year | Type: Necessary cookies
    __Host-1PLSID, __Host-3PLSID

    Crucial cookies to ensure that you remain securely logged into your Google accounts while accessing various Google services.

    Maximum storage duration: 2 Years | Type: Necessary cookies

Functional cookies allow the website to provide enhanced functionality and personalization. They may be set by the website owner or by third parties whose services have been added to the pages.

  • Functional Cookies

    LSOLH

    Used by Google to store session information and enhance the user's experience on Google services.


    Maximum storage duration: Session | Type: Functional Cookies
    COMPASS

    Used by Google to improve user navigation by remembering preferences and information, such as preferred language.

    Maximum storage duration: 6 Months | Type: Functional Cookies
    ACCOUNT_CHOOSER

    Remembers which accounts have been used to log into Google services on the device.

    Maximum storage duration: 1 Year | Type: Functional Cookies
    APISID

    Used by Google to store user preferences and information when viewing pages with Google maps.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    LSID

    Used by Google to store user preferences while viewing pages that incorporate Google services.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    NID

    Used by Google to remember user preferences, such as preferred language, to provide a more personalized experience.

    Maximum storage duration: 6 Months | Type: Functional Cookies
    SAPISID

    Used by Google to collect information about visitors for videos hosted on YouTube or maps integrated with Google Maps.

    Maximum storage duration: 2 Years | Type: Functional Cookies
    __Host-GAPS

    Used by Google to store user preferences and information when pages containing maps or Google services are viewed.

    Maximum storage duration: 2 Years | Type: Functional Cookies

Statistical cookies help website owners understand how visitors interact with the site by collecting and transmitting information anonymously.

  • Statistical Cookies

    CLID

    Unique identifier used to track user interactions and maintain unique sessions.


    Maximum storage duration: 1 Year | Type: Statistical Cookies
    MR

    Microsoft cookie that collects data on user interactions to improve services.

    Maximum storage duration: 7 days | Type: Statistical Cookies
    SM

    Used by the Microsoft Clarity analytics suite to maintain the user's session.

    Maximum storage duration: Session | Type: Statistical Cookies

Marketing cookies are used to track visitors on websites. The intent is to display relevant and engaging ads for the individual user.

  • Marketing Cookies

    AID

    Used by Google to link your activity across devices if you have logged in with the same Google account.


    Maximum storage duration: 1 Year | Type: Marketing Cookies
    ANONCHK

    Used by Microsoft Advertising to check the anonymity of data sent by tracking cookies.

    Maximum storage duration: 10 minutes | Type: Marketing Cookies
    MUID

    Microsoft cookie used to track user interactions across Microsoft domains.

    Maximum storage duration: 13 Months | Type: Marketing Cookies
    __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDTS, __Secure-3PSIDCC

    Google cookies designed to build a profile of your preferences and show you relevant ads on other sites, protecting the Google account.

    Maximum storage duration: 2 Years | Type: Marketing Cookies
    ADS_VISITOR_ID

    Used by Google to identify and track visitors across various websites to display personalized advertising.

    Maximum storage duration: 2 Years | Type: Marketing Cookies
    OTZ

    Used by Google to personalize ads on Google properties, like Google Search.

    Maximum storage duration: 1 Month | Type: Marketing Cookies
    __Secure-1PAPISID, __Secure-1PSID

    Used by Google to deliver more relevant ads and protect the security of your preferences and Google account information.

    Maximum storage duration: 2 Years | Type: Marketing Cookies

Cookies are small text files that can be used by websites to make the user's experience more efficient.

The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This means that cookies classified as necessary are processed under Article 6(1)(f) of the GDPR. All other cookies, namely those belonging to the categories of preferences and marketing, are processed under Article 6(1)(a) of the GDPR.

This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages.

You can change or revoke your consent at any time from the Cookie Statement on our website.

Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.

Specify your consent ID and the date you contacted us regarding your consent.