How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

AngelCam recording API

Cloud Recording endpoints. Requires the Cloud Recording service to be active on the camera — otherwise all endpoints return 404.A camera can have multiple simultaneous recordings (e.g. continuous + event-only) with different retentions. The timeline endpoint returns _segments_ (continuous blocks of recorded video) for a given time range; maximum range per request is 24 hours.

AngelCam recording API is one of 29 APIs that AngelCam publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Recording. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.

This API exposes 15 operations across 15 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 2026.06.11.

Requests are made against a single base URL, https://api.angelcam.com/v1.

15 operations 15 paths 12 schemas 11 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026.06.11
Base URL
https://api.angelcam.com/v1
Authentication
OAuth 2.0, API Key
Resource Areas
1

Authentication & Security 2

AngelCam recording API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode and password flows, exposing 41 scopes. An API key is passed in the header as Authorization (PersonalAccessToken).

  • OAuth2 — See the Authentication section above for full documentation.
  • PersonalAccessToken — Enter your token as: PersonalAccessToken {your-token}

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 11 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

recording 15

Cloud Recording endpoints. Requires the Cloud Recording service to be active on the camera — otherwise all endpoints return 404. A camera can have multiple simultaneous recordings…

GET
/cameras/{camera_id}/recording/deprecated
General recording information
my-cameras-recording-info-deprecated 1 param → 200401403404
GET
/cameras/{camera_id}/recording/download/deprecated
Download a given recording section
my-cameras-recording-download-deprecated 4 params → 200400401403404
POST
/cameras/{camera_id}/recording/start/deprecated
Start recording on given camera
my-cameras-recording-start-deprecated 2 params → 204401403404
POST
/cameras/{camera_id}/recording/stop/deprecated
Stop recording on given camera
my-cameras-recording-stop-deprecated 1 param → 204401403404
GET
/cameras/{camera_id}/recording/stream/deprecated
Create and return recorded stream for a specified time
my-cameras-recording-stream-deprecated 3 params → 200400401403404
GET
/cameras/{camera_id}/recording/timeline/deprecated
Retrieve timeline of records for given camera
my-cameras-recording-timeline-deprecated 3 params → 200400401403404
GET
/cameras/{camera_id}/recordings/
Retrieve recordings on a given camera
my-cameras-recordings-list 1 param → 200401403404
GET
/recording/stream/{streamer_name}/{streamer_id}/deprecated
Retrieve recording stream info
my-cameras-recordings-stream-info 2 params → 200401403404
GET
/recording/{recording_id}/
General recording information
my-cameras-recording-info 1 param → 200401403404
GET
/recording/{recording_id}/download/
Download a given recording section
my-cameras-recording-download 4 params → 200400401403404
GET
/recording/{recording_id}/snapshot/
Retrieve recording snapshot URL at a specified time
my-cameras-recording-snapshot 2 params → 200400401403404
POST
/recording/{recording_id}/start/
Start recording
my-cameras-recording-start 4 params → 204401403404
POST
/recording/{recording_id}/stop/
Stop recording
my-cameras-recording-stop 1 param → 204401403404
GET
/recording/{recording_id}/stream/
Create and return recorded stream for a specified time
my-cameras-recording-stream 3 params → 200400401403404
GET
/recording/{recording_id}/timeline/
Retrieve timeline of records for given recording
my-cameras-recording-timeline 3 params → 200400401403404

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are RecordingResponse (7 properties), RecordingListResponse (4 properties), RecordingStreamResponse (4 properties), ErrorGeneric (3 properties). Each schema is shown below with its type and property counts.

SegmentObject
object
2 properties
Error403PermissionDenied
Error404NotFound
Error400InvalidParams
object
3 properties 3 required
Error401Unauthorized
RecordingDownloadResponse
object
1 property
RecordingStreamInfoResponseDeprecated
object
1 property
RecordingStreamResponse
object
4 properties
RecordingListResponse
object
4 properties 4 required
RecordingTimelineResponse
object
3 properties
RecordingResponse
object
7 properties 4 required
ErrorGeneric
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

angelcam-recording-api-openapi.yml Raw ↑

Other APIs AngelCam publishes across the network.

AngelCam active-service API
AngelCam angelcameras API
AngelCam arrow-clients API
AngelCam audio-message API
AngelCam broadcasting API
AngelCam camera API
AngelCam camera-guest API
AngelCam camera-stream-detection API
AngelCam client API
AngelCam clip API
AngelCam event API
AngelCam incidents API
Where this information came from

This is an independent, third-party profile of AngelCam recording API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.