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

Webex Audio Files API

The Audio Files API from Webex — 4 operation(s) for audio files.

Webex Audio Files API is one of 192 APIs that Webex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Audio Files. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 4 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

7 operations 4 paths 9 schemas 1 DELETE3 GET1 PATCH1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Authentication
OAuth 2.0, HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 5

Webex Audio Files API declares 5 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow. It accepts HTTP bearer tokens (JWT) (bearer-key). It accepts HTTP bearer tokens (BEARER_TOKEN_FROM_CI). It accepts HTTP bearer tokens (JWT) (Bearer). It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearer-key — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • Bearer — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • bearerAuth — JWT bearer token authentication. Obtain your token from the Webex Developer Portal.

Paths & Operations 7

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

Audio Files 7
POST
/organization/{orgid}/audio-file
Create a new Audio File
createConfig_26 1 param body → 200400401403409429500
GET
/organization/{orgid}/audio-file/{id}
Get specific Audio File by ID
getConfig_26 3 params → 200401403404429500
PUT
/organization/{orgid}/audio-file/{id}
Update specific Audio File by ID
updateConfig_26 2 params body → 200400401403404412429500
DELETE
/organization/{orgid}/audio-file/{id}
Delete specific Audio File by ID
deleteConfig_24 2 params → 200401403404412429500
PATCH
/organization/{orgid}/audio-file/{id}
Partially update Audio File by ID
patchConfig_1 2 params body → 200400401403404429500
GET
/organization/{orgid}/audio-file/{id}/incoming-references
List references for a specific Audio File
getIncomingReferences_19 5 params → 200401403404429500
GET
/organization/{orgid}/v2/audio-file
List Audio File(s)
getAllConfigWithMetaData_24 6 params → 200401403404429500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are AudioFileInfoDTO (12 properties), MetaDataReferencesPagingInfo (8 properties), EntityInfo (6 properties), EntityReferenceInfoDTO (3 properties). Each schema is shown below with its type and property counts.

ResponseEnvelopeAudioFileInfoDTO
object
2 properties
ErrorDetails
object
Details of an error.
2 properties
ApiErrorResponse
object
Response body for an API error.
2 properties
AudioFileInfoPatchDTO
object
1 property
MetaDataReferencesPagingInfo
object
Metadata of response for references with paging information
8 properties
EntityReferenceInfoDTO
object
3 properties
EntityInfo
object
6 properties
AudioFileInfoDTO
object
12 properties 2 required
OperationError
object
An error message providing details about the operation failure.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-audio-files-api-openapi.yml Raw ↑

Other APIs Webex publishes across the network.

Webex Address Book API
Webex Admin Audit Events API
Webex Agent Personal Greeting Files API
Webex Agent Summaries API
Webex Agent Wellbeing API
Webex Agents API
Webex AI Feature API
Webex API - Domain Management API
Webex Archive Users API
Webex Attachment Actions API
Webex Authorizations API
Webex Auto CSAT API
Where this information came from

This is an independent, third-party profile of Webex Audio Files 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.