Pre-requisites
WARNING: If these pre-requisites are not met your signal will be discarded and you won't know why.
- Create a service (Profit Sharing, Copy Trading or Signal Provider) in Zignaly
- Create an exchange account in Zignaly with the same Exchange (e.g. Binance) and Exchange type (e.g. futures) that you will be offering as a provider.
- Profit Sharing service: Add funds (As per 2021: 15 USDT should be a minimum to be safe) to your recently created 'Zignaly exchange account' in Zignaly.
- Copy Trader service: Make sure that there are funds (As per 2021: 15 USDT should be a minimum to be safe) in your recently linked exchange account in Zignaly (Usually Binance).
- Signal Provider service: Make sure that there are funds (As per 2021: 15 USDT should be a minimum to be safe) in your recently linked exchange account in Zignaly (Usually Binance).
- Make sure you have selected your new created exchange account (just in case you have several of them)
- You have to follow your own service in Zignaly and allocate to it some of your funds.
- Make your order amount meet the minimal amount required by the Exchange (E.g. Minimum: 0.001 BTC or USDT equivalent for Bitcoin).
If you allocate 100 USDT and you open a Bitcoin position based on 20% of your allocation it will try open a position with 20 USDT. This is not going to work because with current price (1 BTC = 56,955.08 USDT) that means 0.00035136 BTC and that it's way less than the current Binance minimum: 0.001 BTC = 56.91 USDT. You can try to avoid this problem by using LTC instead, using futures and leverage (if you know what you are doing) or increasing your allocated funds.
- I highly encourage you to test the Trading Terminal (making sure you choose your own service and not 'Manual Trading') to feel how Zignaly works. You will learn how it replicates into Binance (In CopyTrading/SignalProvider).
- Even if you are going to create a 'Profit Sharing' service I highly encourage you to create a private Copy Trading service initially as a personal test. That way you can check how Zignaly interacts with Binance (How orders are created, closed and so on). And, again, use the Trading Terminal.
Step 1: Choose your options
Step 2: Choose way to send signals to Zignaly
(+) TradingView strategy - WebHook
Option A) If you want TradingView to handle entries and exits on its own (Zignaly it's only an intermediate tool) you need to set the alert_message attribute from either
- strategy.entry
- strategy.exit
like this:
Suggested signal will be shown here
.
Option B) If you want both Zignaly and TradingView to handle entries and exits you need to set the alert_message attribute from either
- strategy.entry
- strategy.exit
like this:
Suggested signal will be shown here
.
For both options) The associated alert needs to be setup in this way:
- Webhook URL: https://zignaly.com/api/signals.php
- Message: { {{strategy.order.alert_message}} , "key" : "MYSECRETKEY" }
(+) TradingView strategy - Email
Option A) If you want TradingView to handle entries and exits on its own (Zignaly it's only an intermediate tool) you need to set the alert_message attribute from either
- strategy.entry
- strategy.exit
like this:
Suggested signal will be shown here
.
Option B) If you want both Zignaly and TradingView to handle entries and exits you need to set the alert_message attribute from either
- strategy.entry
- strategy.exit
like this:
Suggested signal will be shown here
.
For both options) The associated alert needs to be setup in this way:
- In 'More Actions' check: Send Email-to-SMS
- Message: ||{{strategy.order.alert_message}}||key=MYSECRETKEY||
MYZIGNALYREDIRECTTRIGGER
Suggested workflow for setting up Email from TradingView:
- Setup a new Hotmail account
- Add it as an 'SMS email' in TradingView Profile settings page.
- Confirm your own the email address
- Create a rule in your Hotmail account that: 'Redirects' (not forwards) emails to 'signals@zignaly.email' when
- (1): 'Subject' includes 'Alert'
- (2): 'Email body' contains string 'MYZIGNALYREDIRECTTRIGGER'
- (3): 'From' contains 'noreply@tradingview.com'.
(+) Generic - WebHook
Send a POST request to:
https://zignaly.com/api/signals.php
with this data:
Suggested signal will be shown here
(+) Generic - Email
Send a text-only email to 'signals@zignaly.email' with this body content:
Suggested signal will be shown here
(+) Debug - GET
Warning: Using GET signals is not recommended because of security concerns. Please use only them when debugging.
You can visit:
Suggested signal will be shown here
in your Internet Browser.
Step 3: Read this extra useful information
Step 4: Where to find your MYSECRETKEY
Once you have created a copy-trader or a signal-provider, just to go to your provider edit tab and you will find your service key there under "Signal URL". It's important that you don't share this key with anybody because it controls your service (sending buy/sell orders to the exchange).
Step 5: Just before firing the signal
- Check again if you meet the pre-requisites.
- In Zignaly webpage select the Exchange that follows your own service. Check your Dashboard. Positions. Open. If everything goes ok your position will appear there.
- In Zignaly webpage select the Exchange that follows your own service. Check your Dashboard. Positions. Error Log. If something went wrong you will find why there. Be aware that sometimes the error is so big (Wrong key or syntax) that Zignaly is not going to show it to you.
- Join the discord, check the bug-report channel and ask there if signals are working properly or if they are having an extraordinary delay. This is going to be fixed soon but sometimes there is a 15 minutes delay because of their queue implementation. It's better to know if such a problem is happening before trying to send a signal for the first time. Otherwise you will think you have failed trying to send your signal while you have not and it opens later.
Step 6: Fire the signal
Now you should be ready to fire your first signal.
Beyond the wizard
Donations
You can buy me a coffee (only USDT) at:
BEP2
* Address: bnb136ns6lfw4zs5hg4n85vdthaad7hq5m4gtkgf23
* MEMO: 627502838
BEP20 (BSC)
* Address: 0xd7fb2ba10c97ba1c96ef068a80c06c6ed31bbdc2
ERC20
* Address: 0xd7fb2ba10c97ba1c96ef068a80c06c6ed31bbdc2
TRC20
* Address: TJxJj5BmfM9jgoVwMJycYcyTbzwmz1udWw
or
XMR Address: 84csx9YMDmXQsKUZ4ZyKNwNWbhheTUWBQi1t7k79cvS9CtQbVdKNP5a3G6vZSVRKx9DWV8tuhWe5P3yz7YFoKgMc5kMhSnu
