TWM Wiki

Description

Important Information

Here are some general tips and important points to keep in mind when setting up and using connections in TWM:

Regional Availability & VPN Usage:

Before setting up a connection, please verify that the services of the chosen exchange are available in your geographical region. If access is restricted, you may need to use a VPN (Virtual Private Network).

Copying API Keys and Secrets:

When copying your API keys and secret keys, be meticulous. Ensure that you do not accidentally include any extra spaces (whitespace) before or after the actual key strings, as this will cause authentication to fail.

Initial Historical Data Download:

The first time you request data for a specific trading instrument (e.g., a currency pair like BTC/USDT) through TWM, the software will attempt to download all available historical data for that instrument from the exchange. This happens regardless of the specific time period you initially request. Please allow this comprehensive first download to complete fully before proceeding with further actions or analysis for that instrument.

Type of API Keys (System-Generated vs. Self-Generated):

During the API key creation process on an exchange, you might be asked to choose between system-generated or self-generated (e.g., HMAC vs. Ed25519) API keys. For TWM's purposes, either type is generally acceptable unless specified otherwise for a particular exchange. For details on the differences between these key types, please refer to the information provided by the exchange itself during the creation process.

Naming Your API Keys:

It's good practice to assign a descriptive name to your API keys when you create them on the exchange. While the specific name doesn't affect TWM's functionality, it helps you identify the key for your personal records and management. Some exchanges may even require you to name the key before you can proceed. Always pay attention to prompts and hints in the exchange's user interface to ensure all required fields are completed.

Troubleshooting Connection Issues & API Key Expiry:

If a connection that was previously working suddenly fails, and you've already ruled out IP address filtering as the cause, check the API key configuration settings on the exchange's website. Some exchanges issue API keys that have an expiration date. If your key has expired, you will need to generate a new one.

Understanding Connection Behavior:

Connections without API Keys: If you set up a connection in TWM without entering an API key and secret, TWM will still attempt to connect to the exchange to access public data (like market data feeds). However, you will not be able to execute trades or retrieve private account information (like balances or positions).

Connections with Incorrect/Expired API Keys:

If you do provide API keys but they are incorrect (e.g., mistyped, contain extra spaces) or have expired, the connection will fail. TWM will typically display a generic error message such as "Check your credentials."

Necessary cookies help make the website usable by enabling basic functions such as consent storage, security protection, language preferences, authentication, and preserving the active navigation context.

  • Necessary cookies

    UserUUID

    Technical identifier used to manage and persist cookie consent preferences.

    Maximum storage duration: 12 Months | Type: Necessary cookies
    consent

    Stores your cookie consent choices and selected preferences.

    Maximum storage duration: 12 Months | Type: Necessary cookies
    site_mode

    Preserves the active navigation context, for example keeping the user in the standard website flow or the Start Trading flow when shared navigation elements are used.

    Maximum storage duration: Up to 30 Days | Type: Necessary cookies
    .AspNet.Consent

    Indicates whether the user has provided cookie consent.

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

    Used to prevent CSRF attacks and protect form submissions and user data.

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

    Used to manage authentication information and signed-in sessions.

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

    Stores the user’s language and localization preferences.

    Maximum storage duration: 1 Year | Type: Necessary cookies

Functional cookies allow the website to remember preferences and support enhanced features or integrations such as Google services, maps, embedded media, or account-related personalization.

  • Functional Cookies

    LSOLH

    Used by Google to store session information and support service-related functionality.


    Maximum storage duration: Session | Type: Functional Cookies
    COMPASS

    Used by Google to remember settings and improve navigation across integrated services.

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

    Remembers which Google accounts have been used on the device.

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

    Used by Google to store preferences and information when using integrated Google services such as Maps.

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

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

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

    Used by Google to remember preferences such as preferred language and interface settings.

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

    Used by Google services to support embedded content, maps, and account-related personalization.

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

    Used by Google to support service preferences and related functionality on pages integrating Google services.

    Maximum storage duration: 2 Years | Type: Functional Cookies

Statistical cookies help us understand how visitors interact with the site, measure performance, and improve services. Depending on configuration, data may be processed in aggregated or pseudonymized form.

  • Statistical Cookies

    CLID

    Microsoft Clarity identifier used to distinguish visitors and support analytics reporting.


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

    Microsoft cookie used for analytics-related measurement and service improvement.

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

    Used by Microsoft Clarity to maintain the current analytics session.

    Maximum storage duration: Session | Type: Statistical Cookies
    ttcsid

    TikTok identifier used for event measurement, session attribution, and analytics reporting.

    Maximum storage duration: Varies by configuration | Type: Statistical Cookies
    ttcsid_D5GFV53C77U3VC0C2T50

    TikTok event and analytics cookie used for session-level attribution and measurement.

    Maximum storage duration: Varies by configuration | Type: Statistical Cookies

Marketing cookies are used for advertising, campaign attribution, conversion tracking, personalization, and cross-platform measurement by providers such as Google, Microsoft, Meta, and TikTok.

  • Marketing Cookies

    AID

    Used by Google to link activity across devices and improve ad attribution.


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

    Used by Microsoft Advertising to validate and support ad-related requests.

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

    Microsoft advertising identifier used to recognize browsers across Microsoft domains.

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

    Google advertising and personalization cookies used to build preference profiles and support ad delivery.

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

    Used by Google to identify visitors for advertising and attribution purposes.

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

    Used by Google to support ad personalization and service optimization.

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

    Google cookies used to support more relevant ads and account-related ad security.

    Maximum storage duration: 2 Years | Type: Marketing Cookies
    IDE, DSID, FLC

    DoubleClick / Google Ads cookies used for campaign attribution, ad delivery, and remarketing.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    datr, fr, sb, xs

    Meta / Facebook cookies used for browser recognition, security, ad measurement, and personalization across Meta services and partner sites.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    odin_tt

    TikTok cookie used for campaign attribution, browser recognition, and advertising performance measurement.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    tt_chain_token

    TikTok cookie used for event attribution and campaign linkage across sessions.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    ttwid

    TikTok browser identifier used for attribution, advertising measurement, and remarketing support.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    NID, UULE

    Google cookies that may support ad personalization, localization, and service preference handling depending on the integration and browser state.

    Maximum storage duration: Varies by cookie | Type: Marketing Cookies
    SEARCH_SAMESITE

    Google cookie used to support secure cookie handling across requests and service interactions.

    Maximum storage duration: 6 Months | Type: Marketing Cookies
About cookies and consent

This website uses cookies and similar technologies to ensure its proper functioning and, with your consent, to support functionality, measure usage, improve performance, and provide advertising, attribution, or personalized content. The legal basis for the use of necessary cookies is the legitimate interest of the data controller (Art. 6(1)(f) GDPR), while functional, statistical, and marketing cookies are used only upon your explicit consent (Art. 6(1)(a) GDPR).

Cookies are small text files stored on your device to make the website work efficiently and improve your experience. Some cookies are placed directly by us, while others may be set by third-party services integrated into our pages.

Cookie categories
  • Necessary cookies: enable core site functionality such as consent storage, navigation context, language selection, authentication, and access to secure areas. These cannot be disabled.
  • Functional cookies: allow the website to remember settings and support integrations such as embedded or third-party services.
  • Statistical cookies: collect usage and performance data to help understand and improve the site.
  • Marketing cookies: support advertising, campaign attribution, personalization, and remarketing across providers and services.
Storage and consent management

Your cookie preferences are stored locally in a cookie named consent, valid for 12 months, and pseudonymously on our systems using a technical identifier (UserUUID), which does not allow direct identification of the user. A technical cookie named site_mode may also be used to preserve the current navigation context across pages. You may change or withdraw your consent at any time via the cookie settings button visible at the bottom left of the site.

Third-party cookies

Some cookies are provided by third-party services such as Google, Microsoft, Meta, and TikTok. These third parties may act as independent controllers for the data collected through their own technologies and services.

Your rights

You can withdraw or modify your consent at any time, delete cookies through your browser settings, and exercise your rights under Articles 15–22 GDPR (access, rectification, deletion, limitation, opposition, portability) by contacting us via the details provided in the Privacy Policy.

This Cookie Policy is aligned with Regulation (EU) 2016/679 (GDPR) and the ePrivacy Directive.