Docs › Setup guides › TrendSpider setup

TrendSpider setup

Put your HoldAlarms webhook URL into TrendSpider instead of your endpoint's URL. HoldAlarms answers TrendSpider as soon as the alert is queued, then forwards the message unchanged to your destinations and retries if they fail.

1. Why it helps

TrendSpider alert webhooks time out after five seconds (TrendSpider: webhooks for alerts), and TrendSpider's alert webhook docs describe no retries. If your endpoint is slow or down, that alert is lost. Strategy Bots can retry a failed webhook a few times, 3 seconds apart, with a 7-second timeout (TrendSpider: Strategy Bots). HoldAlarms gives your endpoint 10 seconds per attempt and retries up to 5 times, 2 to 60 seconds apart.

2. Alerts: add the webhook URL

  1. In TrendSpider, click the user icon in the top-right corner and open Account & Settings.
  2. Tick Webhook under Email and SMS.
  3. Paste the URL from the "Your webhook URL" panel on your HoldAlarms dashboard. It looks like https://api.holdalarms.com/hook/<your token>.
  4. In each alert you want delivered, put the message your endpoint expects in the alert's description (the "Your Note" field).

TrendSpider uses one webhook URL for all alerts on your account. Keep it secret: the token in it identifies your HoldAlarms account.

3. Strategy Bots

For a Strategy Bot, choose Webhook as the notification and paste the same HoldAlarms URL as the entry and exit webhook URL. Put the body your destination expects in the Webhook Body field. HoldAlarms answers within the Strategy Bot's 7-second limit, so its own retries are rarely needed.

4. The message

TrendSpider sends the alert's description as the body. It uses application/json when the description is valid JSON (the alert dialog shows "valid JSON"), otherwise text/plain. HoldAlarms forwards the body unchanged with the same content type. TrendSpider's own headers (X-requester, X-reason) are not passed on.

TrendSpider fills in variables such as %alert_name%, %alert_symbol%, %alert_note%, %price_action_event% and %last_price% before sending. For example:

{"ticker": "%alert_symbol%", "action": "buy", "price": "%last_price%"}

Put values your endpoint needs in the message, not in the URL. Query parameters you add to the HoldAlarms URL (such as ?symbol=%alert_symbol%) are accepted but not forwarded.

5. Allowlists

TrendSpider sends from one IP address, 3.12.143.24. If your endpoint only accepts that address, it will reject HoldAlarms, because HoldAlarms has no fixed outbound IP addresses. Turn the IP filter off on your endpoint and check the request another way, for example with a secret in the message.

6. Test it

Click "Send test alert" on the dashboard, then trigger a TrendSpider alert and check it under recent alerts. You can also check your own endpoint first with the free Webhook Checker.

Step-by-step guide with common problems: TrendSpider webhook alerts: setup and retries.

HoldAlarms is not affiliated with TrendSpider. TrendSpider is a trademark of its owner.

← TradingView setup · MetaTrader setup →

HoldAlarms is not affiliated with TradingView. TradingView is a trademark of TradingView, Inc.