Introduction

Before we begin, please read the other articles to understand how the Aurox indicator works. The alerts are based on our indicator and without a proper understanding of it, you WILL lose money.

The alerts require 15 Urus tokens to access them. The tokens can be in your web3 based wallet, they can be staked or if you're providing liquidity to our Uniswap market.

To Sign Up For Alerts Visit Our Terminal On Your Desktop: https://web.getaurox.com

Connecting Your Web3 Wallet

  1. Click on "Scanners" on the bottom bar of the terminal.

2. Click on "Alerts" on the right-hand side.

3. It will prompt you to connect your wallet. You will require either MetaMask or TrustWallet. Some other wallets also utilize TrustWallet integration. If you have issues connecting your wallet please contact support@getaurox.com

4. Once the wallet is connected, it will verify whether you have 15 Urus tokens and give you access.

Setting Up Alerts

Let's go through each part one at a time.

  1. Coins - You'll be able to select the coins you want in this dropdown.

  2. Type: During this selection, you will be able to select to receive alerts on either Aurox indicator, S/R lines, or both.

    The Aurox indicator is pretty straightforward, whenever a long or short triggers, you will receive an alert.

    With S/R lines, you will receive an alert when the price crosses either the support or resistance area.

  3. Confirmed: Checking this box will only send alerts when a signal is confirmed. As always, we only suggest paying attention to confirmed alerts.

    Confirmed alerts trigger when the Aurox indicator has triggered on a candle/interval, and that specific candle ends. The Aurox indicator can trigger at any time during a specific interval, but it is not confirmed until that interval ends.

    Unconfirmed alerts should only be used to notify you that a confirmed signal might happen soon. Unconfirmed signals can happen often, unconfirmed signals are only available for higher intervals, otherwise, your inbox will be flooded with alerts. Please make sure you read our guides above before using unconfirmed signals!

  4. Group Alerts: This option allows you to group alerts into one notification. Therefore if multiple coins trigger within approximately 10 minutes of each other, you will not get 10 separate emails. You will only receive one email with all of the signals that happened during that timeframe.

  5. Intervals: This allows you to select the intervals on which to trigger the alerts. As stated before, selecting 30 minutes, 1 hour, and 4 hours will automatically enable the "confirmed" checkbox because unconfirmed signals are not allowed on these intervals.

  6. Timezone - This is only necessary for email alerts. Each alert will include a timestamp in the email to notify you when the alert triggered

  7. Email address: This is tied to the account you are using. This is bound to the account and will not be interchangeable. If you require to change the email address, you will have to sign up with the appropriate email address on the Aurox platforms.

  8. Webhooks: You can enable webhooks for both Aurox Indicator and S/R Lines. Please read the next section on how the webhooks work. Do NOT set up webhooks and use a bot to start trading off of them unless you have read our guides and are extremely knowledgeable about what you are doing! Especially on intervals less than 1 day.

    Webhooks and bots require not just alerts but they require proper strategies which require backtesting. Several bot-based platforms support webhook signals such as 3commas.

    Make sure to test the webhook endpoint to check if it's receiving the alerts properly.

After you have selected the appropriate settings, simply click save and wait for the alerts to come in.

How To Properly Utilize The Alerts

Please read the previous guides because they are absolutely necessary to utilize the alerts properly.

We recommend for all new traders to utilize only confirmed signals on any interval. Do not under any circumstances receive an alert, pull up your phone, and immediately place an order. You should always confirm your trade via other indicators such as DI, TD Sequential, and even pay attention to the news.

The Aurox indicator, and therefore the alerts, although 70-80% accurate on the daily and weekly, is not a full-proof plan. If it could detect 100% of the movements, we wouldn't be selling it, let alone giving it away. It still takes effort to successfully utilize it, and we have given everyone guides on how to properly do that.

Additionally, if you use these alerts in some bot or algorithm, make sure you use other indicators to confirm the trades and backtest them. We are not liable for losses because users plug-in just these alerts into their bot and have them trade on every trigger!

Our team mainly uses confirmed alerts on BTC, and ETH on 1 day, 1 week, and 1-month intervals. After we are notified of the alert, we immediately pull up our charts and make trades depending on our other market analysis. This is the only recommendation for any new trader.

Using Webhooks

If you're new to webhooks, please Youtube a few guides on how webhooks works. The easiest way to set up webhooks to forward them to specific applications such as SMS, Twitter, Slack, etc.. is through Integromat (Free for most items) or Zapier (paid).

Below, we'll go over the Integromat integration.

Once you have the webhook connection set up, you can send the notification to any channel that Integromat allows. Please refer to guides from Integromat if you require any assistance on how to use them, but in general, it's fairly easy to use.

Setting Up Alerts With 3Commas

Customizing Webhook Requests

Users are able to set a custom and precise webhook request to be sent to them in an event of an alert being triggered. Both Aurox Indicators and R/S Lines support custom webhooks. Every webhook request has a base JSON that custom webhooks can derive from and be sent to their recipients.

Aurox Indicator Custom Webhooks Introduction

By default the JSON schema of Aurox indicator webhook requests are like this:

{

"pair": "{/pair}",

"timeUnit": "{/timeUnit}",

"signalUpdate": "{/signalUpdate}",

"timestamp": "{/timestamp}",

"isConfirmed": "{/isConfirmed}"

}

It shows a JSON with five properties that for the value of part of each something like "{/something}" is used. This is a variable (placeholder).sing something called JSON Pointers. You don't need to read the specification to understand how they work.

A JSON Pointer retrieves the value from an object using the given path.

If you have the following object:

{

"something": {

"in": {

"multilevel": "AWESOME"

}

}

}

and the following payload with your absolute JSON Pointer:

{

"text": "This is { /something/in/multilevel }."

}

Will produce the following :

{

"text": "This is AWESOME"

}

The { /something/in/multilevel } is replaced with the actual value ("AWESOME" ) from the first object.t

The value does not need to be a string and can be a more complex structure like another object.

It is now clear for you that the values ({/pair},{/timeUnit},{/signalUpdate}) will be replaced with the actual data it points to.

For each webhook request, Aurox Alert Engine makes an object available with the given properties from which you can construct your custom payloads:

Aurox Indicator Variables

pair: <string>

The trading pair of the triggered signal. It’s a USDT denominated coin with no separators in between.

example : BTCUSDT, ETHUSDT

timeUnit:<string>

The time unit of the triggered signal.

Possible values:

'30_minute', '1_hour', '4_hour', '12_hour', '1_day', '1_week', '1_month'

signalUpdate: <string>

The type of trigger of the Aurox indicator.

Possible values: "long" , "short"

timestamp: <number>

The unix timestamp of the trigger.

isConfirmed: <boolean>

The confirmation state of the trigger.

Example:

Slack expects a specific payload for their messaging api. Assuming there was trigger for BTCUSDT on 30 minute time unit, the following will need to be used to have it in the general channel:

{

"text" : "{/pair} at {/timeUnit} triggered {/signalUpdate} in {/timestamp}",

"channel": "general"

}

Aurox Resistance and Support Webhooks

By default the JSON schema of Aurox Resistance and Support webhook requests are like this:

{

"pair": "{/pair}",

"timeUnit": "{/timeUnit}",

"support": "{/support}",

"resistance": "{/resistance}",

"timestamp": "{/timestamp}",

}

pair: <string>

The trading pair of the triggered signal. It’s a USDT denominated coin with no separators in between.

example: BTCUSDT, ETHUSDT

timeUnit:<string>

The time unit of the triggered signal.

Possible values:

'30_minute', '1_hour', '4_hour', '12_hour', '1_day', '1_week', '1_month'

support:<number>

New support level for the given pair in USDT. optional and might not be present in all requests.

resistance:<number>

New resistance level for the given pair in USDT. optional, might not be present in all requests.

timestamp: <number>

The unix timestamp of the trigger.

Example:

Assuming there was a new R/S levels for BTCUSDT and is going to be sent to slack this is the payload slack expects to be sent:

{

"text": "{/pair} has new Support level at {/support} and resistance level at {/resistance} in the {/timeUnit} time",

"channel":"general"

}

If you have any questions or need any help, please contact our support (support@getaurox.com).

Did this answer your question?