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

The Locations API from Webex — 4 operation(s) for locations.

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

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

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

10 operations 4 paths 9 schemas 2 DELETE4 GET2 POST2 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
Resource Areas
1

Authentication & Security 3

Webex Locations 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 accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearer-key — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • bearerAuth — e.g. Bearer YOURAUTHORIZATIONTOKEN

Paths & Operations 10

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

Locations 10
GET
/locations
List Locations
listLocations 4 params → 200400401403404405409410
POST
/locations
Create a Location
createLocation 1 param body → 201400401403404405409410
GET
/locations/{locationId}
Get Location Details
getLocationDetails 2 params → 200400401403404405409410
PUT
/locations/{locationId}
Update a Location
updateLocation 2 params body → 204400401403404405409410
DELETE
/locations/{locationId}
Delete Location
deleteLocation 2 params → 204400401403404405409410
GET
/locations/{locationId}/floors
List Location Floors
listLocationFloors 1 param → 200400401403404405409410
POST
/locations/{locationId}/floors
Create a Location Floor
createLocationFloor 1 param body → 201400401403404405409410
GET
/locations/{locationId}/floors/{floorId}
Get Location Floor Details
getLocationFloorDetails 2 params → 200400401403404405409410
PUT
/locations/{locationId}/floors/{floorId}
Update a Location Floor
updateLocationFloor 2 params body → 200400401403404405409410
DELETE
/locations/{locationId}/floors/{floorId}
Delete a Location Floor
deleteLocationFloor 2 params → 204400401403404405409410

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are PostCommonLocationObject (8 properties), FloorUpdated (4 properties), Floor (4 properties), PutCommonLocationObject (4 properties). Each schema is shown below with its type and property counts.

Floor
object
4 properties 1 required
FloorCreationRequest
object
2 properties 1 required
PostCommonLocationObject
object
8 properties 5 required
FloorUpdated
object
4 properties 1 required
FloorCollectionResponse
object
1 property
PutCommonLocationObject
object
4 properties
FloorUpdateRequest
object
2 properties 1 required
LocationsCollectionResponse
object
1 property
Location
object
Location associated with the hot desking member.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-locations-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 Locations 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.