Projects, cameras and exids

The two objects everything else hangs off, and the identifier you will use everywhere.

Almost every Evercam request names a project or a camera, and both are identified by an exid rather than a numeric id.

exid

An exid is a short, stable, human-readable string — evercam, dorset-street-i, kilpo-kbqrd. It is what appears in URLs:

/v2/projects/{project_exid}/cameras
/v2/cameras/{camera_exid}/recordings/snapshots/latest

Objects also carry a numeric id, but that is internal. Use the exid.

Projects

A project is a construction site: a name, a location and a set of cameras.

GET/v2/projectsDash API

Every project your account can see.

GET/v2/projects/{project_exid}Dash API

One project.

Cameras

A camera belongs to a project and carries a status and a timezone.

GET/v2/projects/{project_exid}/camerasDash API

The cameras in one project.

GET/v2/cameras/{camera_exid}Dash API

One camera, with its full configuration.

Status is not a promise of imagery

status describes the camera, not the archive. A camera reporting online may still have no stored snapshot, and a decommissioned camera often has years of history. Check availability rather than inferring it from status — see Snapshots, recordings and timelapses.

Timezone

Each camera carries its own timezone, and snapshot timestamps are expressed in it — not UTC, and not the caller's zone.

Convert before comparing across sites

Two cameras on different sites can report the same wall-clock time for moments hours apart. Normalise using each camera's timezone before comparing or sorting across projects.