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 Multimedia Profile API

The Multimedia Profile API from Webex — 7 operation(s) for multimedia profile.

Webex Multimedia Profile API is one of 193 APIs that Webex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

10 operations 7 paths 17 schemas 1 DELETE5 GET3 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 Multimedia Profile 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 10

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

Multimedia Profile 10
GET
/organization/{orgid}/multimedia-profile
List Multimedia Profile(s)
getAllConfig_6 5 params → 200401403404429500
POST
/organization/{orgid}/multimedia-profile
Create a new Multimedia Profile
createConfig_11 1 param body → 200400401403409429500
POST
/organization/{orgid}/multimedia-profile/bulk
Bulk save Multimedia Profile(s)
saveAllConfig_10 1 param body → 207400401403409429500
GET
/organization/{orgid}/multimedia-profile/bulk-exportdeprecated
Bulk export Multimedia Profile(s)
bulkExport_10 3 params → 200401403404429500
POST
/organization/{orgid}/multimedia-profile/purge-inactive-entities
Purge inactive Multimedia Profile(s)
purgeInactiveConfig_5 2 params → 200400401403409429500
GET
/organization/{orgid}/multimedia-profile/{id}
Get specific Multimedia Profile by ID
getConfig_12 2 params → 200401403404429500
PUT
/organization/{orgid}/multimedia-profile/{id}
Update specific Multimedia Profile by ID
updateConfig_12 2 params body → 200400401403404412429500
DELETE
/organization/{orgid}/multimedia-profile/{id}
Delete specific Multimedia Profile by ID
deleteConfig_11 2 params → 200401403404412429500
GET
/organization/{orgid}/multimedia-profile/{id}/incoming-references
List references for a specific Multimedia Profile
getIncomingReferences_9 5 params → 200401403404429500
GET
/organization/{orgid}/v2/multimedia-profile
List Multimedia Profile(s)
getAllConfigWithMetaData_13 6 params → 200401403404429500

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are MultimediaProfileDTO (16 properties), MultimediaProfileExportDTO (13 properties), MultimediaProfileChannelDTO (9 properties), MetaDataReferencesPagingInfo (8 properties). Each schema is shown below with its type and property counts.

MultimediaProfileDTO
object
16 properties 8 required
MultimediaProfileChannelDTO
object
9 properties 4 required
EntityInfo
object
6 properties
ResponseEnvelopeMultimediaProfileDTO
object
2 properties
MultimediaProfileExportDTO
object
13 properties
MetaDataReferencesPagingInfo
object
Metadata of response for references with paging information
8 properties
Link
object
8 properties
Response
object
3 properties
EntityReferenceInfoDTO
object
3 properties
BulkResponseItemDTO
object
5 properties
BulkRequestItemDTOMultimediaProfileDTO
object
3 properties
ApiErrorResponse
object
Response body for an API error.
2 properties
ErrorDetails
object
Details of an error.
2 properties
BulkResponseDTO
object
1 property
BulkRequestDTOMultimediaProfileDTO
object
1 property
OperationError
object
An error message providing details about the operation failure.
1 property
BulkExportDTOMultimediaProfileExportDTO
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-multimedia-profile-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 Audio Files API
Webex Authorizations API
Where this information came from

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