Platform and ingest APIs
Why Evercam has two families of API, and which one you need.
Evercam's APIs split into two families. Knowing which you are in explains most of the differences in base URL, authentication and response shape.
Platform APIs — data you read
Cameras, imagery, history and analysis. These are the APIs behind everything you see in the Evercam dashboard.
| API | For | Base URL |
|---|---|---|
| Dash | Projects, cameras, snapshots, recordings, media hub | https://media.evercam.io |
| AI | Detection, ANPR, analytics | https://data.evercam.io/v2 |
| Labs | Emerging capabilities, ahead of core promotion | https://labs.evercam.io |
| ExNVR | On-premise recorder | your own device |
Ingest APIs — data you send
Uploads that Evercam then processes: 360 walkthroughs, BIM models and drone flights.
| API | For | Base URL |
|---|---|---|
| 360 | Walkthrough captures | https://ingest.evercam.io/360 |
| BIM | Building models | https://ingest.evercam.io/bim |
| Drone | Aerial surveys | https://ingest.evercam.io/drone |
Practical consequences
One token covers most of the platform. The JWT from the Dash login endpoint is also accepted by the AI API and Labs — with different headers. ExNVR is the exception: it issues its own token per device. See Authentication.
Ingest base URLs include a path prefix. https://ingest.evercam.io/360 is
the base, so an upload path appends to it rather than replacing it.
Ingest authentication is not enforced server-side
The ingest specifications declare bearer authentication and the service does not enforce it server-side. Send the header on every request, and do not treat it as an access control.
AI agents get one surface, not eight. The
MCP server at https://mcp2.evercam.io/mcp sits
in front of Dash, AI, Labs and 360 ingest and presents them as a single set of
tools, so an agent does not have to know which family an answer comes from.
Browse everything in the API reference.