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

Wazo Moh API

The moh API from Wazo — 3 operation(s) for moh.

Wazo Moh API is one of 113 APIs that Wazo publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include moh. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, a changelog, authentication docs, and an AsyncAPI specification.

This API exposes 8 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.1.

Requests are made against a single base URL, /1.1.

8 operations 3 paths 4 schemas 2 DELETE3 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1
Base URL
https://{wazo_stack}/api/auth/0.1
Authentication
API Key
License
Resource Areas
1

Authentication & Security 1

Wazo Moh API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Auth-Token (wazo_auth_token). By default, every request must be authenticated.

Paths & Operations 8

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

moh 8
GET
/moh
List MOH classes
list_moh 7 params → 200
POST
/moh
Create MOH class
create_moh body → 201400
GET
/moh/{moh_uuid}
Get MOH class
get_moh 2 params → 200404
PUT
/moh/{moh_uuid}
Update MOH class
update_moh 2 params body → 204400404
DELETE
/moh/{moh_uuid}
Delete MOH class
delete_moh 2 params → 204400404
GET
/moh/{moh_uuid}/files/{moh_filename}
Get audio file
get_moh_files 3 params → 200404
PUT
/moh/{moh_uuid}/files/{moh_filename}
Add or update audio file
update_moh_files 3 params body → 204404
DELETE
/moh/{moh_uuid}/files/{moh_filename}
Delete audio file
delete_moh_files 3 params → 204404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are MohItems (2 properties), MohFile (1 property). Each schema is shown below with its type and property counts.

MohItems
object
2 properties 1 required
Moh
Error
array
MohFile
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wazo-moh-api-openapi.yml Raw ↑

Other APIs Wazo publishes across the network.

Wazo Phone Provisioning API (wazo-provd)
Wazo Websocket Event Stream (wazo-websocketd)
Wazo Aastra API
Wazo Access Features API
Wazo Action API
Wazo Adhoc Conferences API
Wazo Admin API
Wazo Agent Statistics API
Wazo Agents API
Wazo Applications API
Wazo Asterisk API
Wazo Backends API
Where this information came from

This is an independent, third-party profile of Wazo Moh 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.