AngelCam event API
Events represent detections reported by cameras or sensors — typically motion detected by a camera or a trigger from an external sensor. Events are the building blocks for [RTS incidents](#tag/incidents) and camera timeline markers.## Sending events to AngelcamWhen a camera or sensor detects something, it reports it to Angelcam by calling the event endpoint with its unique `hash` (found in the Angelcam dashboard or via the [Sensor](#tag/sensor) endpoints). Use `POST /v1/events/` in all cases where possible. A `GET /v1/events/` alternative exists solely for devices that are technically incapable of making POST requests (some older cameras). The rate limit for event submission is 10 requests per minute per hash.## Listing eventsPagination for event list endpoints works differently from other list endpoints: there is no `offset` parameter. Instead:- Use the `next` link in the response to move to the next page. - Pagination is one-directional (forward only). - Use the `start` and `end` filters to narrow down the time range.Events are returned ordered by `occurred_at` (newest first).
AngelCam event API is one of 29 APIs that AngelCam publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Event. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.
This API exposes 3 operations across 2 paths, and defines 9 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 event 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 3
Across 2 paths, the API surfaces 3 operations — 2 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Events represent detections reported by cameras or sensors — typically motion detected by a camera or a trigger from an external sensor. Events are the building blocks for [RTS in…
Schemas 9
The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are EventObject (7 properties), EventListResponse (4 properties), Error400InvalidParams (3 properties), ErrorGeneric (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 event 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.