API Catalog

Underlay Connectivity Services are network services independent of the SD-WAN Service and can have a large number of "characteristics" or "attributes" that define their configuration and behavior. Reference MEF 70.2, Section 12.1 UCS Service Attributes

A UCS is connected to a UCS UNI by a UCS End Point. Some service architectures support multiple UCSs at the same UCS UNI. The UCS End Point captures Service Attributes at the UCS UNI whose value can differ between UCSs. Reference MEF 70.1 Section 14 UCS End Point Service Attributes.

Access to an Underlay Connectivity Service is provided at the SD-WAN Edge via the UCS UNI. Reference MEF W70.2 Section 12.2 SD-WAN UCS UNI Service Attributes.

This file forms part of MEF 116 LSO Cantata and LSO Sonata Product Inventory API

This API implements Business Requirements that are defined in MEF Standard: MEF 81

It allows the Buyer to retrieve the information about existing Product instances from Seller's Product Inventory.

Supported use cases:

• Retrieve Product List
• Retrieve Product by Identifier

Copyright 2022 MEF Forum and its [...]

This file forms part of Mplify 160

This API implements Business Requirements described in Mplify 110

Product Offering Availability Discovery is a way for the Buyer to specify a Product Specification to the Seller and to receive from the Seller a list of zero or more Product Configurations.

Pricing Discovery allows the Buyer to receive from the Seller a list of one or more terms and [...]

This file forms part of Mplify 141.1

This API implements Business Requirements described in MEF 134.

Bill is a legal document generated by the Seller to the Buyer relating to charges associated to Products provided by the Seller to the Buyer.

This file forms part of Mplify 142

This API implements the Business Requirements described in Mplify 127.1.

Supported use cases:

• Retrieve List of Product Categories
• Retrieve Product Category by Product Category Identifier
• Retrieve List of Product Offerings
• Retrieve Product Offering by Product Offering Identifier
• Retrieve List of Product Specifications
• Retrieve Product [...]

This file forms part of MEF W175

This draft represents MEF work in progress and is subject to change.

This API implements Business Requirements described in MEF 113 and MEF 173

It allows the Buyer to retrieve CIM Incident as well as register for event notifications related to CIM Incidents.

This file forms part of Mplify 116.1

This API implements Business Requirements described in MEF 81 and MEF 81.0.1

It allows the Buyer to retrieve the information about existing Product instances from Seller's Product Inventory.

List of supported use cases:

• Retrieve Product List

• Retrieve Product by Identifier

Copyright 2025 Mplify Alliance and its contributors.

This file includes [...]

This file forms part of Mplify 123.1 This API implements Business Requirements described in MEF 57.2 and Mplify 57.2.1

Product Order Management allows the Buyer to request the Seller to initiate and complete the fulfillment process of an installation of a Product Offering, an update to an existing Product, or a disconnect of an existing Product at the address defined by the Buyer.

List of [...]

This file forms part of Mplify 115.1 This API implements Business Requirements described in MEF 80 and Mplify 80.0.1 Quote API allows the Buyer to submit a request to find out how much the installation of an instance of a Product Offering, an update to an existing Product, or a disconnect of an existing Product will cost. List of supported Use Cases:

• Create Quote
• Retrieve Quote List
• [...]

This file forms part of Mplify 121.1 This API implements Business Requirements described in Mplify 150

It allows the Buyer to retrieve address information from the Seller, including exact formats, for addresses known to the Seller.

List of supported use cases:

• Validate Geographic Address
• Retrieve a Geographic Address Validation
• Retrieve a Geographic Address by Identifier
• Register for [...]