Cisco states that Webex adds the spark:kms scope to an integration's selected scopes so it can interact with encrypted content, that the generated authorization URL includes it, and that a developer who builds the authorization URL themselves must include spark:kms when the APIs they call require access to encrypted content.

Checked 2026-09-16

Vendor
Cisco
Product
Webex Calling
Subsystem
API surface
Deployment
not restricted
Region
not restricted
Release range
not restricted
Checked
2026-09-16

Sources

Cite this note

APA

WarmTransfer. (2026, September 16). Webex Calling administration APIs and scopes: source note wxapi-kms-scope-is-added-silently. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxapi-kms-scope-is-added-silently

BibTeX

@misc{warmtransfer-claim-wxapi-kms-scope-is-added-silently,
  title  = {Webex Calling administration APIs and scopes: source note wxapi-kms-scope-is-added-silently},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/claims/wxapi-kms-scope-is-added-silently},
  note   = {Source note wxapi-kms-scope-is-added-silently, checked 2026-09-16}
}

Read in context