/api/v1/statusValidate a key and inspect the scope it resolves to.
Run event-security scans from your backend, fetch saved briefs, and render the current risk picture inside customer portals, venue sites, and internal operations tools.
1. Create a key
Generate a scoped key from your workspace. Keys inherit the issuing org and sub-org.
2. Run or fetch
Run a scan on demand or fetch a stored scan created by Live Monitor, bulk upload, or the UI.
3. Render safely
Call SignalGuard from your server. Send only the fields your public page should display.
First request
LiveSend API keys as Bearer tokens. Keep keys on your server only. Do not put sk_live_* keys into browser JavaScript, static HTML, or mobile apps.
Keys are scoped to the workspace and sub-org active when they are created. Reads and writes cannot cross that scope.
Create a replacement key, deploy it, confirm traffic, then revoke the old key from /api-keys.
/api/v1/statusValidate a key and inspect the scope it resolves to.
/api/v1/scanRun an event-security scan and persist the result under the key's workspace.
/api/v1/scan/{scanId}Fetch a stored scan with per-signal severity, headline, generated timestamp, and raw signal payload.
/api/v1/events?limit=20List saved events in scope, including latest scan id, latest severity, venue coordinates, event timing, and Live Monitor status.
Public sites should call SignalGuard from a backend route, then render a reduced status object. This keeps your API key private and lets you decide which details are safe for a public audience.
Node / Express example
Push scan.completed and alert.fired events to customer systems.
Browser-safe tokens for read-only public status widgets.
Typed JavaScript helpers generated from the OpenAPI contract.