X-Git-Url: https://gerrit.onap.org/r/gitweb?a=blobdiff_plain;f=docs%2Fclamp%2Facm%2Fapi-protocol%2Facm-rest-apis.rst;h=1770c756729fd392c665cbdd80369c6a9c52089b;hb=a43eb545dded63e1f21b7f14105ae0ed093b54db;hp=b71dae957190f3dd36b6d8e3a8ef5032f494c132;hpb=2f86c5990a3b01be0226d7c299764e3b0807e1b9;p=policy%2Fparent.git

diff --git a/docs/clamp/acm/api-protocol/acm-rest-apis.rst b/docs/clamp/acm/api-protocol/acm-rest-apis.rst
index b71dae95..1770c756 100644
--- a/docs/clamp/acm/api-protocol/acm-rest-apis.rst
+++ b/docs/clamp/acm/api-protocol/acm-rest-apis.rst
@@ -19,7 +19,11 @@ reference to the Automation Composition Type. The incoming TOSCA is verified and
 referential integrity. On delete requests, a check is made to ensure that no Automation
 Composition Instances exist for the Automation Composition Type to be deleted.
 
-.. swaggerv2doc:: swagger/acm-comissioning.json
+.. csv-table::
+   :header: "Commissioning API"
+   :widths: 10
+
+   `ACM-R Commissioning Swagger <./local-swagger.html#tag/Automation-Composition-Definition>`_
 
 
 Instantiation API
@@ -45,7 +49,11 @@ A call to the update endpoint for a Automation Composition Instance follows the
 here: :ref:`4.1 Management of Automation Composition Instance Configurations
 <management-acm-instance-configs>`.
 
-.. swaggerv2doc:: swagger/acm-instantiation.json
+.. csv-table::
+   :header: "Instantiation API"
+   :widths: 10
+
+   `ACM-R Instantiation Swagger <./local-swagger.html#tag/Automation-Composition-Instance>`_
 
 
 Instantiation Automation Composition Instance Lifecycle Management
@@ -88,7 +96,12 @@ GUI. The API provides filtering so that specific Participants and Automation Com
 can be retrieved. In addition, the quantity of statistical information to be returned can be
 scoped.
 
-.. swaggerv2doc:: swagger/acm-monitoring.json
+.. csv-table::
+   :header: "Monitoring API"
+   :widths: 10
+
+   `ACM-R Monitoring Swagger <./local-swagger.html#tag/Participant-Monitoring>`_
+
 
 Pass Through API
 ================
@@ -103,28 +116,4 @@ Composition.
    The Swagger for the Pass Through API will appear here.
 
 
-Participant Standalone API
-==========================
-
-This API allows a Participant to run in standalone mode and to run standalone Automation
-Composition Elements.
-
-Kubernetes participant can also be deployed as a standalone application and provides REST endpoints
-for onboarding helm charts to its local chart storage, installing and uninstalling of helm charts
-to a Kubernetes cluster. It also allows to configure a remote repository in Kubernetes participant
-for installing helm charts. User can onboard a helm chart along with the overrides YAML file, the
-chart gets stored in the local chart directory of Kubernetes participants. The onboarded charts can
-be installed and uninstalled. The GET API fetches all the available helm charts from the chart
-storage.
-
-.. swaggerv2doc:: swagger/k8sparticipant.json
-
-
-Participant Simulator API
-=========================
-
-This API allows a Participant Simulator to be started and run for test purposes.
-
-.. swaggerv2doc:: swagger/participant-sim.json
-
 End of Document