What the webhook represents
The webhook is an event notification, not a market data stream and not an order execution instruction. It contains the rendered alert message or the exact payload supported by the current channel implementation.
Webhook notifications
Connect crypto alerts to your workflow with webhooks
A webhook sends an HTTP request to your configured endpoint after an AlertoWatch alert triggers. Use it to connect rule matches with automation platforms, internal tools, logs, or notification relays.
Reliable event handling
AlertoWatch accepts an alert event before notification processing. Treat downstream webhook handling as an integration boundary and design receivers to tolerate duplicate or delayed notifications where external systems retry their own work.
Security recommendations
- use HTTPS
- keep endpoint secrets outside frontend code
- return a timely success response
- log event identifiers from your receiving system when available
How it works
- 1
Add a webhook notification channel.
- 2
Enter and test the HTTPS endpoint using the current UI.
- 3
Select the webhook on an alert.
- 4
Process the request when the alert event triggers.
Honest limitations
Third-party endpoint availability, network failures, and endpoint behavior can affect delivery. Webhooks should be treated as notifications, not as a guaranteed trade-execution transport.
FAQ
Can a webhook trigger an automation workflow?
Yes. A receiving system can process the supported webhook payload and start its own workflow.
Can a webhook message be JSON?
Webhook content follows the configured channel template and current product behavior for rendered notification messages.
Does the webhook place orders?
No. AlertoWatch sends a notification request. Any downstream action is controlled by the receiving system.