@@ -15,4 +16,8 @@ OpenSlice makes extensive use of TMFORUM's models and APIs. Therefore if one is
To deliver NaaS we need to incorporate various APIs (see TMF909 API Suite Specification for NaaS). OpenSlice implements various TMF APIs to deliver NaaS and support the lifecycle functions required to manage the network capabilities exposed as Network as a Service and managed by operational domains.
For a complete list of supported APIs, see [Supported APIs](exposed_apis.md)
No newline at end of file
## What's next
* For a complete list of supported APIs, see [Supported APIs](exposed_apis.md)
* Check the defined user roles of OpenSlice in our [Terminology](../terminology.md)
/serviceCatalogManagement/v4/serviceCatalog List or find ServiceCatalog objects
/serviceCatalogManagement/v4/serviceCategory List or find ServiceCategory objects
```
## Example Use Case
Scenario: A service provider wants to offer a new managed XXXX service to enterprise customers.
@@ -20,3 +44,8 @@ Scenario: A service provider wants to offer a new managed XXXX service to enterp
* Service Delivery/Order: Provision Service by Using the orchestration system to provision and configure the XXXX service based on customer orders.
## What's next
* Read the model of Service Catalogs in TMF [TMF633 Service Catalog API User Guide v4.0.0](https://www.tmforum.org/resources/specification/tmf633-service-catalog-api-user-guide-v4-0-0/)
* Check a demo of the API [here](http://portal.openslice.io/tmf-api/swagger-ui/index.html?urls.primaryName=tmf-api-633-ServiceCatalogManagement-v4.0.0)
* Check a demo of the Catalog and Categories [here](http://portal.openslice.io)