API
StormSight is API-first. Every UI surface is backed by a documented REST endpoint. Use this to build your own automation. Auth: an authenticated session cookie from email + password sign-in at /auth/signin. API tokens are not yet available.
Events
GET
/api/eventsGET
/api/events/{id}GET
/api/events/{id}/parcelsGET
/api/events/{id}/export.csvGET
/api/events/{id}/export.pdfGET
/api/events/{id}/impactMonitor Zones
GET
/api/saved-sitesPOST
/api/saved-sitesPUT
/api/saved-sites/{id}DELETE
/api/saved-sites/{id}Forecast
GET
/api/forecast/warningsGET
/api/forecast/outlooksGET
/api/forecast/siteGET
/api/hyperlocal?lat&lonLeads
GET
/api/leadsPOST
/api/leadsGET
/api/leads/{id}PATCH
/api/leads/{id}DELETE
/api/leads/{id}POST
/api/leads/bulkAI Assistant
POST
/api/ai/chatPOST
/api/ai/analyze-photoStreaming
GET
/api/streamGET
/api/feedGET
/api/heatmapVector Tiles
GET
/api/tiles/events/{z}/{x}/{y}GET
/api/tiles/mesh-live/{z}/{x}/{y}Operations
POST
/api/uploadGET
/api/statusGET
/api/healthGET
/api/docsWebhook signatures
Outbound webhooks (event.detected, lead.created, etc.) include an X-StormSight-Signature header containing the HMAC-SHA256 hex digest of the raw body keyed with your subscription’s secret. Always verify before acting on a webhook delivery.