Skip to content

Key concepts

A space is the organisational unit in Angelcam — it owns all resources: cameras, locations, recordings, services, and billing. Every user has their own space by default. Users can be invited to share other spaces with different permission levels (managed through the My Angelcam web UI).

Every API request operates within the authenticated user’s active space. All resource endpoints — cameras, locations, recordings, services — return data that belongs to the active space only. Use the Activate space endpoint to switch context; the selection is persisted server-side.

The Get space permissions endpoint returns all permissions the authenticated user has within a space. Permissions can be scoped at three levels:

Scopelocation_idcamera_id
Whole spacenullnull
Specific locationsetnull
Specific camerasetset

Note: Inviting users to a space and assigning permissions is currently only available through the My Angelcam web UI.

A camera is the central resource. Cameras connect to the platform either directly over the internet (via RTSP or HTTP) or through an Arrow client device such as an AngelBox. Once connected, the API provides access to live streams, snapshots, recordings, and events.

Locations group cameras. Every camera belongs to exactly one location, and every user has a root location — its ID is available from the Current User Info endpoint.

Locations can be armed or disarmed. When armed, Real Time Security (RTS) notifications are active for cameras in that location. Each location can also have a schedule for automatic arming/disarming.

Services are paid features you activate and assign to cameras. The two main camera services:

  • Cloud Recording — stores footage to the cloud. Required for recording, timeline, and clip endpoints.
  • Broadcasting — enables high-concurrency streaming. Required for broadcasting endpoints.

To enable a service on a camera:

  1. Browse available services to find the service code.
  2. Activate the service with the code and a billing period (P1M = monthly, P1Y = annual).
  3. Assign it to a camera with camera_id.

Arrow client is an open-source application that connects devices behind NAT to the Angelcam cloud. See the Arrow clients guide for pairing and proxy details.

RTS is Angelcam’s alarm and notification system built on three concepts:

  • Notification methods — where alerts go (email or HTTP webhook)
  • Notification rules — conditions that trigger an alert (e.g. camera goes offline, motion detected)
  • Incidents — security events created when a rule triggers

When a rule fires, Angelcam creates an incident and delivers a message via the configured notification methods. Locations can be armed or disarmed to suppress or enable RTS for the cameras they contain.