· 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
◆ Webhooks
Stop polling. Register an HTTPS endpoint and AlgoVault POSTs you a signed event the instant a new trade call fires, the regime shifts, or a scheduled scan completes — every delivery is HMAC-signed, idempotent, and retried. Needs a free or paid av_live_ key (get one in your account).
Events
trade_call | A new BUY/SELL trade call is recorded for an asset you track. |
regime_shift | The market regime for (coin, timeframe, exchange) changes vs the previous call. |
scan_digest | A scheduled scan completes — the ranked top-N calls for a timeframe/exchange at your chosen cadence. |
Subscribe
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
}'Filters are optional — omit them to receive every call. assets accepts coin symbols or a top:N token (N 1–100); min_confidence is 0–100. For scan_digest add timeframe, exchange, top_n (1–100) and cadence (1h/4h/1d). The response includes a per-subscription secret — store it to verify signatures.
Manage
GET /api/webhooks | List your active subscriptions. |
DELETE /api/webhooks/:id | Remove a subscription. |
POST /api/webhooks/:id/test | Send a sample delivery to your endpoint to verify wiring. |
Delivery & signature
Each delivery is a POST to your URL with these headers:
X-AlgoVault-Event | The event type. |
X-AlgoVault-Delivery | Unique delivery id — use it as an idempotency key. |
X-AlgoVault-Timestamp | Unix seconds; reject deliveries outside your tolerance to stop replays. |
X-AlgoVault-Signature | HMAC-SHA256(secret, "{timestamp}.{rawBody}") in hex — recompute and constant-time compare before trusting a payload. |
{
"event": "trade_call",
"delivery_id": "d_8f3c...",
"data": {
"type": "trade_call",
"coin": "BTC",
"timeframe": "15m",
"exchange": "BINANCE",
"call": "BUY",
"confidence": 72,
"regime": "TRENDING_UP",
"verify_url": "https://algovault.com/verify?id=..."
}
}Endpoint URLs must be HTTPS (SSRF-guarded; internal addresses are rejected). Full reference — payload schemas, retry/backoff, and self-healing — in docs/WEBHOOKS.md →
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.