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 audio-message API

Endpoints for managing audio messages. Audio messages are pre-recorded audio clips that can be played through [speakers](#tag/speakers).Audio files are uploaded as Base64-encoded content. Supported formats: AAC (`audio/aac`), MP3 (`audio/mpeg`), WAV (`audio/wav`), OGG (`audio/ogg`), and WebM audio (`audio/webm`).Keep audio files short — a few seconds is ideal. Large files will increase upload time and may affect playback reliability.

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

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

This API exposes 4 operations across 2 paths, and defines 8 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.

4 operations 2 paths 8 schemas 2 GET1 POST1 PUT

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 audio-message 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 4

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

audio-message 4

Endpoints for managing audio messages. Audio messages are pre-recorded audio clips that can be played through [speakers](tag/speakers). Audio files are uploaded as Base64-encoded…

GET
/audio-messages/
Retrieve audio messages
audio-message-list 2 params → 200400401403
POST
/audio-messages/
Create a new audio message
create-audio-messages body → 201400401403
GET
/audio-messages/{message_id}/
Retrieve audio message
audio-message-detail 1 param → 200400401403404
PUT
/audio-messages/{message_id}/
Update existing audio message
update-audio-message 1 param body → 200400401403404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are AudioMessageListResponse (4 properties), ErrorGeneric (3 properties), Error400InvalidParams (3 properties), AudioMessageObject (3 properties). Each schema is shown below with its type and property counts.

Error403PermissionDenied
AudioMessageWriteObject
object
2 properties 2 required
Error404NotFound
Error400InvalidParams
object
3 properties 3 required
AudioMessageListResponse
object
4 properties 4 required
Error401Unauthorized
ErrorGeneric
object
3 properties 3 required
AudioMessageObject
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

angelcam-audio-message-api-openapi.yml Raw ↑

Other APIs AngelCam publishes across the network.

AngelCam active-service API
AngelCam angelcameras API
AngelCam arrow-clients 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
AngelCam location API
Where this information came from

This is an independent, third-party profile of AngelCam audio-message 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.