The Email Bot will trade based on received emails. If the subject or message contains a defined message the bot will execute the corresponding action. This action will only be allowed to execute when the bots coin/funds position is on the opposite side. The bot can handle an unlimited amount of actions from one or multiple sources.
Supported Trade Types
Create a unique name for your bot.
Select the account on which the bot should run.
Select which market this bot should run on.
Specify the leverage for the bot.
Select the coin where the funds are located at this moment.
Select the current funds position. No Position is when you do not have any Long or Short Positions. Should be used as the start of any trade bot unless you manually opened a position
HTS supports 3 types of trade amount options.
The static option uses a fixed amount where the sell amount is adjusted for fees.
All-in uses 99% of the available coins.
With maximum amount the bot will use what’s available in the wallet with a maximum of X coins.
How much the bot has to trade with.
The current trade amount after corrections.
This template will be used when the bot executes a stop-loss order.
Fee percentage of the bot. Only used in backtests and for bots running on simulated accounts.
Minimum price change required before buy orders are executed.
Minimum price change required before sell orders are executed.
The maximum percentage the price is allowed to drop before the bots execute a sell order to prevent more losses.
The minimum profit percentage the position has to reach before its allowed to be closed.
The maximum loss percentage the position may have before its forced to close.
Possibility to restrict from who the email is fetched.
Definition on which the emails are matched. A message can be defined in 3 ways
Exact match (case insensitive)
Wildcard. Use an * as a wild card. For example
Regular expressions. For example:
The bots action after the email has been received
Type of orders you want this bot to place. Standard limit and market orders are available as well native exchange and custom templates defined in the Order Template Builder.
When there are multiple messages defined and the timespan is set, all the messages need to be received within that time span. If the time between the first and last email is larger than the defined seconds the signal won’t be valid. If the timespan is set on 0, the action can be executed by one of the messages.