Protect signals with a secret key

Plus and Pro only

For the Core/Plus/Pro plans, this feature is included with Plus and Pro. Check your plan in Portal.

Legacy subscriptions: existing Advanced and Professional subscriptions retain their documented access. Check the subscription shown in Portal before changing plans.

Signal Authentication checks that the secret= value in an alert message matches the key saved in PineConnector Portal. When it is enabled, a missing or incorrect key prevents the signal from being forwarded to MetaTrader.

Your License ID selects the destination. Your secret key is a separate value used to authenticate the signal. Do not use one in place of the other.

Before you enable it

The published guide documents support from PineConnector EA v3.15. Check the feature’s availability in your subscription and the version on the intended connection.

Every affected alert needs the matching key

Once Signal Authentication is on, existing alerts without the correct secret= are withheld. Prepare the affected alert messages before relying on the setting. Changing the key in Portal does not update your TradingView alerts.

Choose your own secret and keep it private. The published guide recommends at least eight characters and a mixture of character types. Use the format accepted by Portal; do not copy a sample key from a guide as your real key.

Configure the key in Portal

1. Open Signals in PineConnector Portal.
2. Select Signal Modifier.
3. Find Signal Authentication and enter your chosen Secret Key.
4. Turn authentication On and select Save when your affected alerts are ready to use the same key.

Enlarge

Published interface example. SECRETKEY is a placeholder, not a recommended secret.

Published interface example. SECRETKEY is a placeholder, not a recommended secret.Open original Close Esc

The key is case-sensitive. A capital letter, lowercase letter or extra character makes a different value.

Add the key to your alert message

Add secret=YOUR_SECRET_KEY to the PineConnector alert message, replacing the placeholder with the exact key saved in Portal. Do this in TradingView, not in a form on this documentation site.

This example requests a buy of 0.01 lots using the current explicit-volume syntax. Replace the broker symbol and use a permitted demo size. The secret is a separate authentication value; it does not change trade size.

If you maintain older risk=-based alerts, retain their reviewed sizing and EA settings, and add only the matching secret= field. Legacy parameter guidance.

Message template with authenticationReplace LicenseID, EURUSD and YOUR_SECRET_KEY for your demo setup before using this template.

TradingView → Message PineConnector Syntax

LicenseID,buy,EURUSD,vol_lots=0.01,secret=YOUR_SECRET_KEY

If your message comes from Pine Script, add the parameter to the generated message. Recreate the TradingView alert after changing the script or its inputs so the alert uses the updated snapshot.

The docs do not need your secret

A saved License ID for examples does not supply or validate your authentication key. Keep the key out of screenshots, support messages and pages copied into ChatGPT or Claude. Replace it with YOUR_SECRET_KEY when sharing an example for help.

Verify authentication and the trade separately

Use a demo account and the test-alert workflow.

1. Confirm the alert uses the intended License ID and matching secret.
2. Check the signal’s result in the Signal Log.
3. If it passes authentication, check MetaTrader for the expected order.
4. Confirm the account, symbol, direction, volume and targets, with no unintended duplicate.

Passing the secret-key check does not guarantee execution. Other syntax, EA settings or broker rules can still prevent the order.

Missing or incorrect key

Signal Log result / situation	What to check
Authentication is on, but no secret= was sent	Add the parameter to the alert that actually fired.
The secret does not match	Compare the key with Portal exactly, including case and extra characters.
The message still uses an old key	Update that alert; changing Portal alone does not change it.
A script was updated but the alert still sends the old value	Recreate the alert with the updated script/inputs.

The published guide says missing and incorrect keys are withheld and recorded in the Signal Log. Correct the source of the message before sending another demo test. Do not disable authentication merely to make an unexplained failure disappear.

Change a secret safely

Identify every alert that uses the old key, prepare their replacement messages, and coordinate the Portal change with those alerts. Confirm the new key with a demo test before returning to the intended automation.

If the old key was shared accidentally, replace it rather than continuing to use it. Never post either key when asking Support to investigate; share the error and a redacted example instead.

Watch the walkthrough

Set up Signal Authentication

Walkthrough linked from the published Signal Authentication guide. The written steps above identify the required key and affected-alert checks.Watch on YouTube

For message structure, use PineConnector Syntax. For a signal that stops elsewhere in the workflow, use Missing signals.