AngelCam location API
Endpoints for accessing and managing locations. Locations are used to organize cameras into groups. Every camera belongs to exactly one location, and every user has a root location whose ID is available from the [Current User Info](#tag/user) endpoint.Locations can be **armed** or **disarmed**. When a location is armed, Real Time Security (RTS) will generate notifications for events on cameras in that location. Each location supports scheduled arming/disarming so notifications can be active only during certain hours.> **Note:** Creating, editing, and deleting locations is currently only possible through the [My Angelcam](https://my.angelcam.com/) web UI. These API endpoints provide read access only.
AngelCam location API is one of 29 APIs that AngelCam publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Location. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.
This API exposes 2 operations across 2 paths, and defines 7 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.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
AngelCam location 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 2
Across 2 paths, the API surfaces 2 operations — 2 GET. Each is listed below with its method, path, parameters, and response codes.
Endpoints for accessing and managing locations. Locations are used to organize cameras into groups. Every camera belongs to exactly one location, and every user has a root locatio…
Schemas 7
The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are LocationObject (7 properties), LocationListResponse (4 properties), ErrorGeneric (3 properties), Error400InvalidParams (3 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from AngelCam 12
Other APIs AngelCam publishes across the network.
This is an independent, third-party profile of AngelCam location 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.