AngelCam active-service API
Endpoints for managing your activated services and assigning them to cameras.A service must first be activated (purchased) for your account, then assigned to a specific camera before it takes effect on that camera.## Service lifecycle1. **Find a service code.** Browse [available services](#operation/services) to get the `code` of the service you want.2. **Activate the service** by calling [`POST /billing/active-services/`](#operation/activate-service). Provide the service `code` and a billing `period` — `P1M` for monthly or `P1Y` for annual billing.3. **Assign to a camera** by calling [`PUT /billing/active-services/{id}/usage/`](#operation/my-service-usage-update) with the `camera_id`. Set `camera_id` to `null` to unassign.4. **Upgrade or downgrade** at any time via [`PUT /billing/active-services/{id}/`](#operation/my-service-update). A downgrade takes effect at the end of the current billing period by default. Set `force_downgrade: true` to apply it immediately with prorated credit.5. **Cancel** via [`DELETE /billing/active-services/{id}/`](#operation/my-service-cancel).
AngelCam active-service API is one of 29 APIs that AngelCam publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include active-service. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and rate-limit docs.
This API exposes 7 operations across 3 paths, and defines 10 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 active-service 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 7
Across 3 paths, the API surfaces 7 operations — 1 DELETE, 3 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
Endpoints for managing your activated services and assigning them to cameras. A service must first be activated (purchased) for your account, then assigned to a specific camera be…
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are ActiveServiceObject (7 properties), ActiveServiceListResponse (4 properties), Error400InvalidParams (3 properties), ActiveServiceUsageObject (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 active-service 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.