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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Rhombus Systems

Rhombus Systems AudioPlayback Webservice API

The AudioPlayback Webservice API from Rhombus Systems — 6 operation(s) for audioplayback webservice.

Documentation Provider Profile APIs.io OpenAPI GitHub

Rhombus Systems AudioPlayback Webservice API is one of 65 APIs that Rhombus Systems publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include AudioPlayback Webservice. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 6 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://api2.rhombussystems.com.

6 operations 6 paths 13 schemas 6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api2.rhombussystems.com/api
Authentication
API Key
Contact
developer@rhombussystems.com
Resource Areas
1

Authentication & Security 1

Rhombus Systems AudioPlayback Webservice API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-auth-apikey (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).

Paths & Operations 6

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

AudioPlayback Webservice 6
POST
/api/audioplayback/cancelLoopingAudioPlayback
Cancel looping audio playback
cancelLoopingAudioPlayback 1 param body → 200
POST
/api/audioplayback/deleteAudioUploadMetadata
Delete audio upload metadata
deleteAudioUploadMetadata 1 param body → 200
POST
/api/audioplayback/getAudioUploadMetadataForOrg
Get audio upload metadata for organization
getAudioUploadMetadataForOrg 1 param body → 200
POST
/api/audioplayback/playAudioUpload
Play audio upload
playAudioUpload 1 param body → 200
POST
/api/audioplayback/updateAudioUploadMetadata
Update audio upload metadata
updateAudioUploadMetadata 1 param body → 200
POST
/api/audioplayback/uploadAudioText
Upload text to synthesize audio
uploadAudioText 1 param body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are AudioUploadMetadataType (10 properties), Audioplayback_UploadAudioTextWSResponse (7 properties), Audioplayback_UploadAudioTextWSRequest (5 properties), Audioplayback_PlayAudioUploadWSResponse (4 properties). Each schema is shown below with its type and property counts.

Audioplayback_UpdateAudioUploadMetadataWSResponse
object
Response from updating audio upload metadata.
3 properties
AudioUploadMetadataType
object
List of audio upload metadata for the organization
10 properties
Audioplayback_CancelLoopingAudioPlaybackWSRequest
object
Request to cancel looping audio playback on audio devices.
1 property
Audioplayback_UploadAudioTextWSRequest
object
Request to upload text for audio synthesis.
5 properties
Audioplayback_UpdateAudioUploadMetadataWSRequest
object
Request to update audio upload metadata.
3 properties
Audioplayback_DeleteAudioUploadMetadataWSResponse
object
Response from deleting audio upload metadata.
3 properties
Audioplayback_CancelLoopingAudioPlaybackWSResponse
object
Response from canceling looping audio playback.
4 properties
Audioplayback_PlayAudioUploadWSRequest
object
Request to play an uploaded audio clip through audio devices.
4 properties
Audioplayback_UploadAudioTextWSResponse
object
Response from uploading text for audio synthesis.
7 properties
Audioplayback_GetAudioUploadMetadataForOrgWSResponse
object
Response containing audio upload metadata for organization.
4 properties
Audioplayback_GetAudioUploadMetadataForOrgWSRequest
object
Request to get audio upload metadata for organization.
Audioplayback_PlayAudioUploadWSResponse
object
Response from playing an uploaded audio clip.
4 properties
Audioplayback_DeleteAudioUploadMetadataWSRequest
object
Request to delete audio upload metadata.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

rhombus-systems-audioplayback-webservice-api-openapi.yml Raw ↑

Other APIs Rhombus Systems publishes across the network.

Rhombus Console WebSocket API
AE Profile APIs.io
Rhombus Systems Access Control Integrations Webservice API
AE Profile APIs.io
Rhombus Systems Access Control Webservice API
AE Profile APIs.io
Rhombus Systems Alarm Monitoring Keypad Webservice API
AE Profile APIs.io
Rhombus Systems Alert Monitoring Webservice API
AE Profile APIs.io
Rhombus Systems AudioGateway Webservice API
AE Profile APIs.io
Rhombus Systems Badge Reader Webservice API
AE Profile APIs.io
Rhombus Systems BLE Webservice API
AE Profile APIs.io
Rhombus Systems Button Webservice API
AE Profile APIs.io
Rhombus Systems Camera Webservice API
AE Profile APIs.io
Rhombus Systems ClaimKey Webservice API
AE Profile APIs.io
Rhombus Systems Climate Webservice API
AE Profile APIs.io
#AudioPlayback Webservice
← Back to R APIs
API Details
ID
rhombus-systems:rhombus-systems-audioplayback-webservice-api
Base URL
https://api2.rhombussystems.com/api
Docs
https://api-docs.rhombus.community/
Provider
Rhombus Systems
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=rhombus-systems-audioplayback-webservice-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/rhombus-systems-audioplayback-webservice-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Rhombus Systems AudioPlayback Webservice 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.