Entry & Exit via Webhook

1. Purpose and Overview

The Webhook feature allows you to open or close trades in OptionsApp through external signals. Rather than triggering entry or exit through conventional filter or trigger logic within the app, the trigger is sent from an external webhook.

The feature can be used in both Entry Conditions and Exit Conditions:

• In an Entry Condition, the webhook serves to open a trade.
• In an Exit Condition, the webhook serves to close a running trade.

A typical use case is connecting external automation or signal services, for example TradingView. However, the feature is not limited to any particular provider.

2. How It Works

Each Webhook Condition is uniquely assigned to an active Session in OptionsApp as well as to a specific Entry or Exit Condition.

After creating a webhook, OptionsApp provides the following information:

• a Webhook URL
• a prepared payload with encrypted assignment values
  • session_key
  • webhook_condition_id

When this webhook is sent by an external system to the specified URL, OptionsApp can uniquely assign the signal to the correct Session and the correct Condition.

This ensures that the signal is processed only where it actually belongs.

3. Use Cases

The Webhook feature can be used in two areas.

4. Setting Up a Webhook

Setup is done in the Configuration section within Entry Conditions or Exit Conditions.

4.1 Navigation

A webhook can be created as follows:

• Switch to the Configuration section
• Open Entry Conditions or Exit Conditions
• Add a new Condition
• In the Condition type selection in the top right, select Webhook instead of Filter or Trigger

After selecting Webhook, the input form adjusts accordingly.

4.2 Creating a Webhook Condition

After selecting Webhook, first assign a name to the Condition.

The following elements are then available:

• the WEBHOOK URL field
• the Copy URL button
• the Create Webhook button
• a section for payload preview

As long as no webhook has been created yet, there is no complete payload.

4.3 Creating a Webhook

Clicking Create Webhook generates the webhook.

OptionsApp then displays:

• the webhook URL used
• the prepared payload with the associated encrypted values

The displayed payload contains the information that the external system must use when sending the webhook.

The assignment is done via:

• session_key to identify the running Session
• webhook_condition_id to identify the specific Webhook Condition

5. Testing the Webhook

After creating a webhook, the Test Webhook function is also available.

This function can be used to check whether the webhook can be processed successfully in principle.

If the test runs successfully, a corresponding message appears confirming that the webhook test was successful.

The test serves to verify the technical reachability and assignment of the webhook before the webhook is used productively by an external system.

6. Using Webhook with TradingView

A typical use case for the webhook is using it with TradingView. There, an alarm can be set up so that when triggered, a webhook is automatically sent to OptionsApp.

To use this, a TradingView account is required that supports alarms and webhook notifications.

6.1 Setting Up an Alarm in TradingView

In TradingView's chart view, a new alarm can be created via the alarm icon on the right.

This is where you define the desired alarm condition, for example when a signal should be triggered.

6.2 Entering the Webhook URL

In the Notifications section of the alarm, the Webhook option must be enabled.

In the Webhook URL field, enter the URL that is displayed in OptionsApp for the corresponding Webhook Condition.

6.3 Inserting the Message

In the Message field of the TradingView alarm, paste the content from the Webhook Payload section of OptionsApp.

This content must be copied exactly as is.

7. Requirements for Execution

For a webhook to be processed in practice, several requirements must be met:

• the respective OptionsApp Session is active
• the webhook was created correctly in an Entry Condition or Exit Condition
• the Condition was saved
• the Condition was assigned to a Strategy or Trade
• the external system sends the webhook to the correct URL with the correct parameters

If any of these requirements are missing, execution cannot occur.

8. Usage Notes

The Webhook feature serves exclusively as a trigger for Entry or Exit logic. The actual trade execution continues to follow the Strategy, Template, and Order logic stored in OptionsApp.

This means in particular:

• the webhook does not replace a Trade Template
• the webhook does not replace a Strategy assignment
• the webhook does not replace already defined trading logic
• the webhook merely provides the external signal for start or closing

For proper usage, you should always verify that the respective Condition is correctly assigned and that the entire Strategy is fully set up.