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 Licenses API

The Licenses API from Webex — 3 operation(s) for licenses.

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

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

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

3 operations 3 paths 13 schemas 2 GET1 PATCH

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, OAuth 2.0
Resource Areas
1

Authentication & Security 3

Webex Licenses API declares 3 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow. It accepts HTTP bearer tokens (JWT) (bearer-key). It supports OAuth 2.0 (bearerAuth) using the authorizationCode flow, exposing 1 scope.

  • bearer-key — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • bearerAuth — OAuth 2.0 Bearer token authentication

Paths & Operations 3

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

Licenses 3
GET
/licenses
List Licenses
List_Licenses 1 param → 200400401403404405409410
GET
/licenses/{licenseId}
Get License Details
Get_License_Details 4 params → 200400401403404405409410
PATCH
/licenses/users
Assign Licenses to Users
Assign_Licenses_to_Users body → 200206400401403404405409

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are LicensewithUsers (10 properties), License (9 properties), UserLicensesResponse (7 properties), PatchUserLicenses (5 properties). Each schema is shown below with its type and property counts.

LicenseProperties
object
3 properties
LicensewithUsers
object
10 properties
License
object
9 properties
LicenseError
LicenseCollectionResponse
object
1 property
ErrorResponse
object
3 properties
Users
object
4 properties
PatchUserLicenses
object
5 properties
SiteUrlsRequest
object
3 properties 2 required
LicenseRequest
object
3 properties 1 required
UserLicensesResponse
object
7 properties
ErrorDetail
object
2 properties
SiteResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-licenses-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 Licenses 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.