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

Cisco Expressway Zones API

Zone configuration for call routing and firewall traversal

Cisco Expressway Zones API is one of 18 APIs that Cisco Expressway publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 7 JSON Schema definitions.

Tagged areas include Zones. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a getting-started guide, a changelog, and 7 JSON Schemas.

This API exposes 15 operations across 5 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 14.2.0.

Requests are made against a single base URL, https://{host}/api.

15 operations 5 paths 10 schemas 3 DELETE5 GET4 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
14.2.0
Base URL
https://expressway.example.com/api/provisioning
Authentication
HTTP Basic
Contact
License
Resource Areas
1

Authentication & Security 1

Cisco Expressway Zones API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic Authentication using Expressway administrator credentials. The API is only accessible via HTTPS.

Paths & Operations 15

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

Zones 15

Zone configuration for call routing and firewall traversal

GET
/provisioning/edge/zone/traversalserver
Cisco Expressway List Expressway-E traversal server zones
listEdgeTraversalServerZones → 200401403
POST
/provisioning/edge/zone/traversalserver
Cisco Expressway Create a traversal server zone on Expressway-E
createEdgeTraversalServerZone body → 200400401409
PUT
/provisioning/edge/zone/traversalserver
Cisco Expressway Update a traversal server zone on Expressway-E
updateEdgeTraversalServerZone body → 200400401404
DELETE
/provisioning/edge/zone/traversalserver
Cisco Expressway Delete a traversal server zone from Expressway-E
deleteEdgeTraversalServerZone → 200401404
GET
/provisioning/controller/zone/traversalclient
Cisco Expressway List Expressway-C traversal client zones
listControllerTraversalClientZones → 200401403
POST
/provisioning/controller/zone/traversalclient
Cisco Expressway Create a traversal client zone on Expressway-C
createControllerTraversalClientZone body → 200400401409
PUT
/provisioning/controller/zone/traversalclient
Cisco Expressway Update a traversal client zone on Expressway-C
updateControllerTraversalClientZone body → 200400401404
DELETE
/provisioning/controller/zone/traversalclient
Cisco Expressway Delete a traversal client zone from Expressway-C
deleteControllerTraversalClientZone → 200401404
GET
/provisioning/common/zone/neighbor
Cisco Expressway List all neighbor zones
listNeighborZones → 200401403
POST
/provisioning/common/zone/neighbor
Cisco Expressway Create a neighbor zone
createNeighborZone body → 200400401409
PUT
/provisioning/common/zone/neighbor
Cisco Expressway Update a neighbor zone
updateNeighborZone body → 200400401404
DELETE
/provisioning/common/zone/neighbor
Cisco Expressway Delete a neighbor zone
deleteNeighborZone → 200401404
GET
/provisioning/common/zone/dns
Cisco Expressway List all DNS zones
listDnsZones → 200401403
POST
/provisioning/common/zone/dns
Cisco Expressway Create a DNS zone
createDnsZone body → 200400401409
GET
/status/common/zones
Cisco Expressway List zone connectivity status
listZoneStatus → 200401403

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are TraversalClientZone (18 properties), NeighborZone (18 properties), TraversalServerZone (17 properties), DnsZone (9 properties). Each schema is shown below with its type and property counts.

TraversalServerZoneInput
object
Input for creating or updating a traversal server zone
2 required
TraversalClientZone
object
Traversal client zone configuration on Expressway-C. Connects to a traversal server (Expressway-E) across a firewall.
18 properties
ZoneStatus
object
Connectivity status for a configured zone on the Expressway
7 properties
TraversalServerZone
object
Traversal server zone configuration on Expressway-E. Enables firewall traversal services for traversal clients.
17 properties
Error
object
Standard error response from the Expressway API
2 properties
TraversalClientZoneInput
object
Input for creating or updating a traversal client zone
4 required
DnsZone
object
DNS zone configuration. Enables endpoint discovery through DNS lookups for SIP and H.323 calls.
9 properties
NeighborZoneInput
object
Input for creating or updating a neighbor zone
2 required
NeighborZone
object
Neighbor zone configuration. Connects the local Expressway to another system such as another Expressway, Unified CM, or gatekeeper.
18 properties
DnsZoneInput
object
Input for creating or updating a DNS zone
1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-expressway-zones-api-openapi.yml Raw ↑

Other APIs Cisco Expressway publishes across the network.

Cisco Expressway SNMP API
Cisco Expressway XML API
Cisco Expressway Admin Account API
Cisco Expressway Alarms API
Cisco Expressway Calls API
Cisco Expressway DNS API
Cisco Expressway Licensing API
Cisco Expressway NTP API
Cisco Expressway Registrations API
Cisco Expressway Resource Usage API
Cisco Expressway Search Rules API
Cisco Expressway SFTP API
Where this information came from

This is an independent, third-party profile of Cisco Expressway Zones 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.