Tradestory

Tradestory Docs

Webhooks are the main mechanism by which you can send data to TradeStory, Trigger Trading Events, and orchestrate your strategy actions.  This can be seen in the Webhooks section of your Strategy.

The main concept is that a Strategy can have many Webhook Endpoints.  When data is sent to any of these Webhook Endpoints, you can configure TradeStory to run Actions.  An example of an Action is to trigger the execution of a Story.

The most obvious example would be to automate signals from external tools like TradingView.

1.Signal from tradingview (or other external tool)

3.TradeStory Webhook Endpoint runs its Action = Run Story to execute a trade on your account.

To add a new Webhook Endpoint to your strategy, navigate to the Webhooks section of your Strategy and click Add Webhook.

Simply give it a name and click Add to save it to your strategy.

Your new webhook endpoint can now be seen in the list. (Note the url is blurred for security. You can hover over it to see it).  This is a unique endpoint generated specifically for you and your strategy and must not be shared with anyone.

You can copy the unique webhook URL by clicking on the link icon.

To delete the endpoint click on the trash icon.

To view logs or see incoming webhook history for the endpoint click on the logs list icon, or history zap icon.

You can turn the endpoint on/off (enable/disable) by toggling on the switch button on the right.  Disabled webhooks will still accept incoming requests, but they will simply not run any of their configured Actions.

Webhooks Overview

Adding a new webhook endpoint

Once you have set up a Webhook Endpoint, you have a unique URL that you can start sending alerts to.  Copy the endpoint URL from TradeStory and paste it into the Alert of any indicator in Tradingview.

Ensure that your alert is set up to only trigger when it should.  This is different for each indicator, but typically you would only want to send a webhook alert

.  In the example below the signal does not require any more data or message.  If your Stories are using data in the payload of a webhook, then you can set this in the message section of the alert.

Setup a Story to run when the signal is received on the Webhook Endpoint

Connecting your Webhook to Tradingview

Assuming you have set up your alerts to hit a TradeStory Webhook Endpoint URL, you can now link the Webhook to execute Stories to do the heavy lifting of processing data, performing logic, or making trades on your accounts.

Click on the title of one of your Webhook Endpoints to open its settings.

Webhook actions are executed each time a Webhook Endpoint receives data or alerts.

By default the Action type is Run Story, which allows you to select a Story to run when the webhook is hit.  Select your story and click Save.  You can add as many actions as you wish into the actions list.  These actions are executed in the order they are in this list.  You can re-order them by clicking and dragging the order.

You can see a summary of the actions in the main Webhook Endpoint item.  In this example, when the “My Awesome Buy Signal” webhook is hit, TradeStory will execute stories “Test Story”, and “Another Test”.

Because those Stories are being triggered from a Webhook being hit, their Context will have all the data and information that is included in the Webhook payload (See 

Running a Story when a Webhook is received

This is for more advanced users.  Just like you can run Stories which have already been saved in response to Webhook Endpoints being triggered, it is also possible to send Story information within the webhook payload itself using TradeScript™!  The payload of the webhook request to your endpoint must contain valid TradeScript™ Story Definitions.  If valid, they will be executed just like a normal story would when the Webhook is triggered.  (So you are sending TradeScript™ as your alert!)

This is extremely powerful because it gives you the ability to fire dynamic data to tradestory from other sources containing complete instructions about what TradeStory should do with your data, and even create your own APIs.

In order to set this up, when creating a new Webhook Action, you need to select a different type of action:

Select Run Webhook Story in the Action Type dropdown and click Save.

You will see this as a summary in your Webhook Endpoint.

The data in your alert or request to the Webhook Endpoint URL must contain valid TradeScript™ definition of a Story.

{
 "story": {
   "story_items": [
     { story_item },
     { story_item },
     { story_item },
     ...
   ]
 }
}


 Make your life easier by writing your base TradeScript™ Story Definition in the visual editor of a temporary story, switching to TradeScript™ mode and copy/pasting this into your webhook alert.

For example this will go into the Message of the Alert from Tradingview:

Webhook Stories - Stories within Webhooks

Webhook Endpoints can also accept other data you wish to send them as part of your strategies.  For example, a BUY signal is good in itself, but you might also want to send information to support the trade, such as a take-profit or stop-loss value, or even a trading lot size.  This is where TradeStory gets extremely powerful, giving you a way to accept external data, and execute Stories to process it and decide to make trades or run other actions based on the content of the data!

To do this, simply ensure the Webhook alert payload sent to your endpoints contains valid JSON data in the following format:

 Sending stop-loss and take-profit levels as part of a webhook alert.

{
 "data": {
   "take_profit": 17660.50,
   "stop_loss": 17600.50,
   "lots": 10
 }
}


In TradingView you can add dynamic values in your alerts: (See Tradingview docs for more info).

{
 "data": {
   "take_profit": {{plot("tp")}},,
   "stop_loss": {{plot("sl")}},
   "lots": {{strategy.position_size}}
 }


You can access these values within your Stories using the Webhook Data item:

Webhook Data - Sending data within Webhooks

To see the history of when your Webhook Endpoints have been triggered, you can click on the history zap icon on your selected webhook.

This displays a log of all webhook triggers.

To drill down into the trigger to see what data was sent in the payload, click again on the zap icon.

Additionally, if you need to see Story Runs that were the result of your webhook being triggered, simply click on the Log stack icon 

of your selected webhook endpoint.  This will take you to the overall Log console with the filters already drilled down into your specific endpoint.