SD-WAN Manager 26.2 API changes

Scope

This page compares the local OpenAPI specifications for:

• SD-WAN Manager 26.1 — specifications dated 2026-01-06
• SD-WAN Manager 26.2 — specifications dated 2026-07-29

The comparison covers all 13 OpenAPI categories in both releases. It matches operations by HTTP method and concrete URL shape, normalizes path-parameter labels, and compares deprecated markers, resolved request and response schemas, and parameter contracts. Descriptions, examples, and titles were excluded from schema-change detection. Counts below come from the local YAML files and were cross-checked against every category page in Cisco’s API changelog.

The Partner Integrations category has 76 operations in 26.1 and 77 in 26.2. Its changes are included in the counts and were cross-checked against Cisco’s Partner Integrations changelog.

What an absent operation means

An operation absent from a 26.2 specification is absent from that published contract. Confirm runtime behavior against a 26.2 Manager before removing production automation that depends on it.

Summary

Change across all 13 categories	Local specification result
New operation signatures	95
Operations absent in 26.2	113
Operations newly marked deprecated	14
Concrete path changes in current Bruno requests	0
Guide examples corrected for a breaking request-body change	1

The largest removals are 57 legacy MultiCloud Edge operations in SD-WAN Services and 38 Cloud OnRamp (COR)/Cortex template operations in UX 1.0 Configuration. New profile operations cover SBC, VPN QoS policy, IPv4 ACL, dying-gasp, and monitoring capabilities. No path-parameter-only rename was counted as a route change.

Two of the 27 monitoring operations that appear new in the local diff — GET /advisories/insecure-config/summary and GET /statistics/download/{processType}/file/{token}/{fileName} — were already listed in Cisco’s 26.1 Monitoring changelog. Their absence from the local 26.1 monitoring file is a source discrepancy, so 95 is a snapshot-diff count, not a claim that all 95 first shipped in 26.2. Cisco’s 26.2 category pages report the same new-operation and deprecation counts as the local diff for all 13 categories; the discrepancy is with the earlier 26.1 monitoring publication.

Cisco’s UX 2.0 changelog also identifies the newly required devices field on configuration-group deployment as a breaking change. The Bruno deployment request already included this field; the guide’s empty-body example has been corrected.

Cisco compatibility classification

Cisco lists breaking changes in 11 of the 13 API categories. Its classification includes request, response, parameter, and operation-ID changes, as well as absent operations. The narrower Learning Hub assessment below checks the paths and payloads exercised by this repository.

Updates

Category coverage

OpenAPI category	New	Absent	Other contract changes
Administration and Settings	0	0	No request, response, or parameter change detected.
Feature Profiles: Mobility and NFV	0	0	LAN/WAN bridge and network-name patterns, switch VLAN validation, and SNMP constraints changed.
Feature Profiles: Others	15	0	Security, policy-object, and application-priority schemas and selected query parameters changed.
Feature Profiles: SD-Routing	10	0	Broad profile validation and response-schema changes, including ACL reference shapes and device support metadata.
Feature Profiles: SD-WAN Service	5	0	Interface ACL, AppQoE, VPN, routing, and other parcel schemas changed.
Feature Profiles: SD-WAN System	0	0	AAA, Global, Logging, NTP, Security, and SNMP parcel schemas changed.
Feature Profiles: SD-WAN Transport	15	0	GPS, VPN, interface, ACL, and routing parcel schemas changed.
Monitoring and Troubleshooting	27	1	Alarm/admin-tech requests, health/search responses, and 11 operation parameter contracts changed.
Others	19	17	Licensing, certificate, control-component, backup, and MultiCloud contracts changed.
SD-WAN Services	2	57	DCA response media types and MultiCloud interconnect validation changed.
UX 1.0 Configuration	1	38	Seven parameter contracts and one response schema changed.
UX 2.0 Configuration	0	0	Group deployment, preview, creation, and group response schemas changed.
Partner Integrations	1	0	Wazuh and Webex request schemas changed; eight operations became deprecated.

Counts represent operation signatures. Schema and parameter changes overlap operations in the same row and are summarized separately.

UX 2.0 groups and feature profiles

Area	26.2 change
Configuration-group deployment	POST /v1/config-group/{configGroupId}/device/deploy now requires a nonempty devices array. Optional deployAssociatedGroups can request deployment of associated Policy or Topology Groups.
Configuration-group create/edit	Adds optional deviceVersion and six supported parcel-type enum values in topology details. Group reads expose deployment timestamps and device status counts.
Configuration and Policy preview	Adds optional deployment/group fields to the request schemas and associatedGroupUnsupportedFeatureTypes to responses.
Policy and Topology groups	Group reads gain deployment timestamps and device status counts. Policy deployment gains optional deployAssociatedGroups; operation paths are stable.
SD-WAN Service	Adds five ios-ipv4-acl parcel operations. Ethernet and SVI ACL fields, AppQoE, VPN, and routing schemas also change.
SD-WAN Transport	Adds ten dying-gasp and five ios-ipv4-acl parcel operations. GPS gains a stream field, with changes to VPN and interface validation.
SD-Routing	Adds ten dying-gasp operations under Transport and cellular-controller paths. Multiple existing profile payloads and response schemas change.
Feature Profiles: Others	Adds VPN QoS policy operations under Application Priority and SBC profile/configuration operations.
SD-WAN System	No operation-set change; several parcel validation schemas change.

The newly added endpoint families are optional capabilities for the current Learning Hub workflows. Existing profile create and parcel URLs remain present.

Monitoring and platform APIs

The 26.2 monitoring file adds CDP/LLDP neighbors, cellular dying-gasp and GPS, NGFW engine/update status, power-management history, QFP classification, switchport/VLAN, alarm purge, notification-rule, and admin-tech operations. It also includes the two monitoring operations already documented for 26.1 above. The long statistics-download route is absent in 26.2; the shorter route is present.

The Others category adds GNSS read operations, truststore certificate and test operations, RADKit authorization management, NGFW signature-package actions, and version-compliance initialization. SD-WAN Services adds two DCA reads: GET /dca/cloudservices/dcscapabilities and GET /dca/settings/configuration/{type}/dca.

For GET /dca/cloudservices and GET /dca/cloudservices/otp, the 26.2 specification uses application/json for the successful response instead of application/octet-stream. Cisco’s SD-WAN Services changelog also flags this media-type change.

Partner Integrations

The local comparison finds one new operation, POST /fedramp/dnssec/actions. It also shows that POST /fedramp/wazuh/config now requires wazuhAgents and wazuhServer, and that the Webex datacenter request gains optional IPv6 prefix fields. These findings match Cisco’s Partner Integrations changelog. No Partner Integrations operation is absent in the 26.2 specification.

Deprecations

Fourteen operations become deprecated in the local 26.2 specifications. Six are outside Partner Integrations:

Category	Newly deprecated operation
Others	POST /util/olapdb/migration/action/{action}
SD-WAN Services	GET /dca/settings/configuration/cloudservices/dca
UX 1.0 Configuration	GET /template/config/diff/{deviceId}
UX 1.0 Configuration	POST /template/device/resource-group/{resourceGroupName}/{templateId}
UX 1.0 Configuration	POST /template/feature/resource-group/{resourceGroupName}/{templateId}
UX 1.0 Configuration	POST /template/policy/vedge/{resourceGroupName}/{policyId}

The new generalized DCA read at GET /dca/settings/configuration/{type}/dca is available while the older cloudservices-specific route remains present but deprecated.

The other eight are Partner Integrations operations:

Area	Newly deprecated operations
Cisco Software	GET /v1/cisco-software/user, GET /v1/device-authorize/authentication, POST /v1/device-authorize/token/{deviceCode}, GET /v1/device-authorize/validtoken
Deployment Mode	GET /fedramp/dnssec/actions, GET /fedramp/wazuh/actions, POST /fedramp/wazuh/config, GET /fedramp/wazuh/status

The local flags match Cisco’s Partner Integrations changelog.

Deprecation is not removal

All 14 operations remain in the 26.2 contract. Plan migration without assuming they are unavailable at runtime.

Removals and replacements

Category	Absent operations	Affected family
SD-WAN Services	57	Legacy MultiCloud Edge account, connectivity, gateway, device-link, location, vWAN, and dashboard operations.
UX 1.0 Configuration	38	/template/cor and /template/cortex Cloud OnRamp operations.
Others	17	Smart Licensing (5), MSLA (4), OLAP DB migration (6), device-security action (1), and firmware action (1).
Monitoring and Troubleshooting	1	GET /statistics/download/{processType}/file/{fileType}/{queue}/{deviceIp}/{token}/{fileName}.
Total	113	Across all 13 categories.

These are operation signatures absent from the local 26.2 files after normalizing path-parameter labels. For the monitoring download route, the shorter GET /statistics/download/{processType}/file/{token}/{fileName} is present in 26.2 and was already documented by Cisco for 26.1. Verify its parameters and response before migrating a caller; the two routes are not assumed interchangeable.

The local files do not declare direct replacements for the removed MultiCloud Edge, COR/Cortex, licensing, MSLA, or OLAP migration families. Cisco’s SD-WAN Services and Others changelogs also identify breaking changes in those areas. An operation can be absent from the published contract without establishing that a running 26.2 Manager rejects it.

Learning Hub impact

Learning Hub area	Impact	Assessment
Authentication, status, and device inventory	None	The paths used by the guides and Bruno requests remain present. GET /device gains optional query parameters; existing calls do not need them.
System feature profile	Low	AAA, Global, and Logging parcel schemas change, but their operation paths remain. Recheck environment-supplied values against 26.2 constraints before claiming runtime support.
Transport feature profile	Low	The WAN VPN and Ethernet parcel paths used by Bruno remain. ACL and validation changes warrant payload review; the new dying-gasp and IPv4 ACL parcels are not used in the current workflow.
Service feature profile	Low	The LAN VPN and Ethernet parcel paths remain. The new IPv4 ACL parcel is optional; existing Bruno payloads do not set the changed ACL fields.
CLI feature profile	None	No CLI operation, request, response, or parameter change was detected.
Configuration-group create and read	Low	Paths remain stable. deviceVersion and deployment-status response fields are additive; the current create request does not need the new field.
Configuration-group deployment guide	Updated	Both deploy examples in 08-deploy-config-group.mdx now send a nonempty devices array, as required by the 26.2 schema.
Configuration-group Bruno deployment	None	Deploy config group/05-deploy-config-group.bru already sends devices: [{"id": "{{device_id}}"}], matching the newly required shape.
Policy and topology groups	Low	Operation paths remain. The new group status fields and optional deployment/preview fields do not invalidate the current examples.
Monitoring guides and Bruno requests	None for current paths	The current system, interface, application-route, and bulk calls remain. New optional GET /device and GET /device/interface parameters do not require edits to existing requests.
Legacy MultiCloud, COR/Cortex, licensing, and OLAP migration	None in this repository	The removed signatures are not used by the current guides or Bruno collection. External automation using those families needs a separate migration review.
Partner Integrations	None in current workflows	The current Learning Hub does not call the new DNSSEC action or changed Wazuh and Webex operations. External Wazuh clients must add the required request fields.

This is a static contract assessment. It does not establish that the Bruno workflows were run successfully against a 26.2 Manager.

Recommended follow-up

1. Smoke-test the Bruno create, associate, variables, deploy, and clean flows against a 26.2 Manager; record the tested build and any runtime differences.
2. Validate environment-supplied System, Transport, and Service parcel values against the changed 26.2 schema constraints before labeling those examples 26.2-compatible.
3. Review any external clients using the 57 MultiCloud Edge, 38 COR/Cortex, 17 Others, or long monitoring-download operations absent from the 26.2 contract.
4. Review external Partner Integrations clients that call the Wazuh configuration operation or newly deprecated Cisco Software and FedRAMP operations. Reconcile the two monitoring operations already documented for 26.1 when reporting release-wide additions.