To integrate your backend, please share:

• BACKEND_URL (base): e.g., https://api.yourdomain.com
• Exact endpoint path for risk: e.g., /portfolio_risk
• Auth details (if any): header name and example value (we’ll store as BACKEND_API_KEY)
• Expected request JSON: sample payload with field names (tickers, start_date/end_date, options, etc.)
• Expected response JSON: sample of the metrics and series you return (volatility series, VaR/CVaR, GARCH/XGB/LSTM forecasts)
• Content-Type: please confirm it returns application/json (not HTML/redirect) on POST

Once I have these, I’ll finalize the proxy at /api/portfolio_risk and point the dashboard fetcher to it.

I updated the proxy to treat BACKEND_URL as the exact backend endpoint (no extra path appended) and changed the dashboard to call the proxy at /api/portfolio_risk. This eliminates the HTML 404 from hitting a non-existent route and aligns with your provided backend URL. If your backend requires an API key, add BACKEND_API_KEY in Vars and the proxy will send it as x-api-key automatically.