· Channels — how you connect
Webhooks
Push AlgoVault trade calls and regime shifts to your endpoint the instant they fire — no polling. Register a URL and receive HMAC-signed POST deliveries with automatic retry and backoff. Subscribe to trade_call and regime_shift events across the monitored venues.
When to use Webhooks vs the other channels
Use Webhooks when you want AlgoVault to push to you — a trading bot that acts on new calls, an alerting or logging pipeline. It is the only outbound channel; MCP and the REST API are pull / request-response. Pair Webhooks with MCP or REST for on-demand queries alongside real-time push.
Connect
curl -X POST https://api.algovault.com/api/webhooks \
-H "Authorization: Bearer av_live_..." \
-H "Content-Type: application/json" \
-d '{
"url": "https://your-server.com/hook",
"events": ["trade_call", "regime_shift"],
"timeframes": ["15m", "1h"],
"assets": ["BTC", "ETH", "top:25"],
"min_confidence": 60
}'Tool coverage
Every publicly-listed tool reachable through Webhooks (equities are held from public listings):
Frequently asked questions
What events can I subscribe to?
trade_call (new BUY/SELL calls) and regime_shift (market-regime changes), across the monitored venues.
How are webhook deliveries secured?
Each POST is HMAC-SHA256 signed with your subscription secret, so you can verify the payload came from AlgoVault.
What happens if my endpoint is down?
Deliveries retry with backoff; persistent failures auto-disable the subscription and are surfaced for review, so a dead endpoint never blocks the queue.
Do webhooks replace MCP or the REST API?
No — they complement them. Webhooks push events to you; MCP and REST are pull. Use webhooks for real-time reaction and MCP/REST for on-demand queries.