Webhooks

Webhook destinations send an alert's message to a URL you choose. They are available on Essential and above, for both Price Alerts and Custom Alerts. See Plans.

For Telegram, Discord or Slack notifications, use their dedicated destination setup.

Create a webhook

1. Open Account Alerts, or choose Add a destination in an alert's Send to section.
2. In Webhooks, enter the receiving URL and an optional name. The endpoint must be publicly reachable on port 80 or 443.
3. For an automation endpoint, enable For bots and trade relays. This uses the faster delivery lane and skips events that could only be delivered late.
4. Choose Add webhook. Copy the signing secret when it is shown; it is shown only once.
5. Create or edit an alert and select this webhook under Send to.

Use a test endpoint or paper setup to check the message before connecting live automation. Send test sends a message to the configured endpoint, so first check how the receiver handles test messages.

Choose a message format

Expand the webhook's message in the alert editor and choose Format. Formats insert an editable template; they do not configure your account or trading bot on the receiving platform.

For a Custom Alert on a strategy, supported formats can use The strategy's order (buy or sell). Only choose that when the alert supplies the strategy order fields. Otherwise select an explicit action. The 3Commas format uses its own entry and exit actions.

Editing a template changes the format label to Your own. Choosing another format replaces the message; Undo restores a custom message that was replaced.

Placeholders and JSON

Use Insert placeholder to choose values supported by the alert, then review Preview and Message checks. For example, a message can include:

{{alert.name}} fired on {{market}} at {{close}}.
Event: {{event.id}}
{{chart_url}}

A body that parses as JSON is sent as application/json; other messages are sent as text. Keep required fields from your receiver's format and check its symbol, action and sizing conventions before saving.

Verify delivery

Each webhook request is signed. If you control the receiver, use the signing secret to verify the X-LuxAlgo-Signature header. Keep the secret private.

Open the alert's History or the Alerts panel's Log to inspect delivery status, attempts and the HTTP response when available. Check the receiver's own logs separately: a successful HTTP response means it accepted the request, not that a trade executed.