Skip to main content
Almost everything you can do in the AcuSight dashboard is backed by a REST API you can call yourself — list devices, manage projects and datasets, run training, and read metrics and detections. This page covers the basics: base URL, auth, and how to find the endpoints.

​
Base URL

All API requests go to your AcuSight host under the /api prefix:
Requests and responses are JSON. Most read endpoints return a { "success": true, "data": … } envelope.

​
Authentication

The API authenticates with a bearer token:
Today that token comes from an authenticated AcuSight session — the same sign-in the dashboard uses. Calls are automatically scoped to your organization; you only ever see your own org’s data, so there’s no org ID to pass. A GET /api/organization is the quickest way to confirm your token works.

​
Get your token

The dashboard keeps your session token where you can copy it in a few seconds:
  1. Sign in at acusight.io.
  2. Open your browser’s developer tools — F12, or Ctrl + Shift + I (Cmd + Option + I on Mac).
  3. Go to the Application tab (Storage in Firefox) → Local Storage → select the acusight.io entry.
  4. Copy the value of acusight_token — that’s your token.
Same token, other route: it also rides every API call the dashboard makes — in the Network tab, pick any /api/… request and copy what follows Bearer in the Authorization request header.
Two things to know about session tokens:
  • They expire. The dashboard refreshes its token silently in the background, but the copy you took doesn’t — when your calls start returning 401, grab a fresh one the same way.
  • They are you. The token carries your identity, your role, and your org scope. Treat it like a password: don’t commit it, share it, or bake it into anything long-running.
Self-serve API keys are coming. A first-class flow for creating long-lived personal or service tokens — for CI, server-to-server jobs, and scripts — isn’t available yet. If you have a machine-to-machine integration in mind, get in touch so we can help and prioritize it.
Device agents use a separate credential (a device key issued during provisioning) that only works for device endpoints. It isn’t a general-purpose API key — don’t use it for your own integrations.

​
Find the endpoints

The full, always-current list of endpoints — with parameters, request bodies, and response shapes — lives in the generated API reference. A few you’ll reach for early:

​
Conventions

  • JSON everywhere — send Content-Type: application/json on writes.
  • Org scoping is automatic — your token determines the org; there’s no org ID to pass.
  • No versioning yet — the API is unversioned today; we’ll announce a versioning scheme before any breaking changes.

​
Next steps

API reference

The full, generated list of endpoints with parameters and responses.

Co-Pilot & MCP

Ask questions about your data, or connect an external AI client.