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

SIP protocol configuration

Cisco Expressway SIP 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 SIP. 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 2 operations across 1 path, and defines 3 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.

2 operations 1 paths 3 schemas 1 GET1 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 SIP 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 2

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

SIP 2

SIP protocol configuration

GET
/provisioning/common/sip/configuration
Cisco Expressway Retrieve SIP configuration
getSipConfiguration → 200401403
PUT
/provisioning/common/sip/configuration
Cisco Expressway Update SIP configuration
updateSipConfiguration body → 200400401403

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are SipConfiguration (9 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
Standard error response from the Expressway API
2 properties
SipConfiguration
object
SIP protocol configuration for the Expressway
9 properties
SipConfigurationInput
object
Input for updating SIP configuration

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-expressway-sip-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 SIP 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.