Updated images and added link from DV page

Author: denise-msft

powerapps-docs/maker/data-platform/dataverse-accelerator/api-playground.md

@@ -6,77 +6,80 @@ ms.author: demora
 ms.reviewer: matp
 ms.service: powerapps
 ms.topic: how-to
-ms.date: 05/13/2024
+ms.date: 05/24/2024
 ms.custom: template-how-to
 contributors:
 - dikamath
 ---
 
-# Test and explore the Dataverse Web API (preview)
+# Explore and test Dataverse in the Web API playground (preview)
 
 [!INCLUDE [cc-beta-prerelease-disclaimer](../../../includes/cc-beta-prerelease-disclaimer.md)]
 
-The API playground is a pre-authenticated software testing tool that helps makers quickly and conveniently interact with the [Microsoft Dataverse Web API](/power-apps/developer/data-platform/webapi/overview). 
+The API playground is a pre-authenticated software testing tool that helps makers quickly and conveniently interact with the [Microsoft Dataverse Web API](/power-apps/developer/data-platform/webapi/overview).
 
-![API playground home screen](./media/api-playground/api-play-landing.svg)
+![API playground home screen](./media/api-play-landing.svg)
 
-This web application allows developers to test and experiment with different API endpoints without the need for extensive setup or authentication processes. It also conveniently presents certain available actions, examples, and links to documentation for faster learning.
+This web application allows developers to test and experiment with different API endpoints without the need for extensive setup or authentication processes. It also conveniently presents certain available actions and links to documentation for faster learning.
 
 Use this tool to explore what's possible in the RESTful API, test user-defined workflows, and more.
 
 > [!IMPORTANT]
 > - This is a preview feature.
 > - [!INCLUDE [cc-preview-features-definition](../../../includes/cc-preview-features-definition.md)]
 
-## Prerequisites
-
-You must have access to the Dataverse Web API and the Dataverse accelerator app.
-
 ## Key features
 
 - Pre-authenticated: The API playground comes pre-authenticated, so developers can start testing and experimenting with API endpoints right away.
 - Web-based: With the API playground, developers can quickly interact with the Dataverse Web API without the need for extensive setup like software downloads or third party account setup. You can access the tool from the Dataverse Accelerator, a first party app available in all new Microsoft Dataverse environments and can be installed in any environment.
 - Convenient: Presents the various actions and capabilities available in the Dataverse Web API, making it easy to quickly learn what's possible and how to implement it.
 
-## Installation
+## Prerequisites
 
-This feature is available in the Dataverse accelerator app. Go to the [Dataverse accelerator article](./dataverse-accelerator.md) for installation instructions.
+You must have [access to Dataverse](/power-apps/maker/data-platform/data-platform-entity-licenses), and [access to run the Dataverse accelerator app](./dataverse-accelerator.md#prerequisites-to-run-the-dataverse-accelerator).
 
 ## Get started
 
-To get started with the API playground, simply run or install the Dataverse Accelerator and navigate to the API playground page to start interacting with the Dataverse Web API.
+To get started with the API playground, [run](dataverse-accelerator.md#play-the-dataverse-accelerator) the Dataverse accelerator and navigate to the API playground page.
 
-### Make web API requests
+### Make requests to the Dataverse Web API
 
-Choose the desired request type to open the request screen. The input options are determined based on the request type. There are three request types presented:
+On the landing screen, choose the request type to open the request editor by clicking the 'Create' button on any of the top cards. 
+
+Three request types are presented:
 
 | Type | Description |
 |-|-|
 | Custom API | This includes any Microsoft Dataverse Web API first party [actions](/power-apps/developer/data-platform/webapi/use-web-api-actions), [functions](/power-apps/developer/data-platform/webapi/use-web-api-functions), or any public [user-defined Custom APIs](/power-apps/developer/data-platform/custom-api) registered in the working environment. |
 | Instant low code plugin | [Instant low code plugins](/power-apps/maker/data-platform/low-code-plug-ins?tabs=instant) are classified as any user-defined workflows registered as a Custom API in the environment with a related FxExpression. |
-| OData request | Provides an interface with more paramaters than the other types, allowing more granular control to create and send [OData requests](/power-apps/developer/data-platform/webapi/perform-operations-web-api). |
+| OData request | Allows more granular control over the request inputs to send [OData requests](/power-apps/developer/data-platform/webapi/perform-operations-web-api). |
 
 ### Request a Custom API or instant low code plugin
 
 These request types are designed to simplify calling plugins available in the working environment.
 
 1. Select an option from the main dropdown, which presents the available plugins in the current environment.
-   ![Custom APIs are listed in the dropdown](./media/api-playground/api-play-list-customapi.svg)
+   ![Custom APIs are listed in the dropdown](./media/api-play-list-customapi.svg)
+
+1. If parameters are available, they are displayed in the *Query params* table that appears. Provide values for required parameters.
 
-1. If parameters are available, they are displayed in the *Query parameters* table that appears.
+    ![Custom API parameters will dusplay automatically](./media/api-play-customapi-params.svg)
+
+    > [!NOTE]
+    > Checkboxes to the left of each parameter indicate whether they are included in the request. Required parameters have disabled checkboxes, while optional parameters have editable ones.
 
 1. Click **Send**
 
-Observe the [response](#view-the-response) in the lower section of the screen.
+1. Observe the [response](#view-the-response) in the lower section of the screen.
 
-![Parameters are listed if registered](./media/api-playground/api-play-response.svg)
+    ![Parameters are listed if registered](./media/api-play-response.svg)
 
 > [!NOTE]
-> The interface provides convenience by listing the available plugins and auto-populating the associated parameters definitions. However, behind the scenes an OData call is still being made.
+> The interface provides a convenient listing of all available plugins in the environment. When selected, the associated parameters with data types are presented. Behind the scenes an OData call is still being made, but the interface simplifies the construction of the call.
 
 ### Make an OData request
 
-OData requests allow more control over the request parameters.
+OData requests allow more options for request parameters.
 
 1. Select the *HTTP request method* in the first dropdown.
 
@@ -86,10 +89,10 @@ OData requests allow more control over the request parameters.
 
     1. In the Url
         1. After the question mark (`?`) character in the Url, type in the query parameter key.
-        ![Key typed into Url after question mark](./media/api-playground/api-play-key.svg)
+        ![Key typed into Url after question mark](./media/api-play-key.svg)
         1. Type an equals (`=`) character after the key
         1. Type in the value
-        ![Value typed into Url after the equals sign](./media/api-playground/api-play-value.svg)
+        ![Value typed into Url after the equals sign](./media/api-play-value.svg)
 
         The keys and values will automatically populate the parameter table in the interface.
 
@@ -103,41 +106,34 @@ OData requests allow more control over the request parameters.
 
 After a request is sent, the response is displayed in the lower half of the screen.
 
-![OData response](./media/api-playground/api-play-odata-response.svg)
+![OData response](./media/api-play-odata-response.svg)
+
+The response status provides quick metrics on the request:
 
-1. The response status provides quick metrics on the request:
-    1. Status message (e.g., "200 Success")
-    1. Duration (in milliseconds)
-    1. Size (in kilobytes)
-1. The response body is displayed in an editor control below the response status.
-    1. View in prettified JSON or in raw form by selecting the mode in the dropdown.
-    2. Click the copy icon to copy the response body to clipboard.
+- Status message
+- Duration (in milliseconds)
+- Size (in kilobytes)
+
+The response body is displayed below the response status. You can click the copy icon to copy the response body to your clipboard.
 
 ### Save an API request
 
 You can save requests for quick access later on. Saved requests will store the request details (such as the request method and endpoint for OData request, or the selected plugin for Custom API and instant low code plugin), and the input parameters with associated values.
 
 1. In the request screen, click the save button in the top right corner of the page.
-1. A side rail will appear inline on the right side of the page with form fields
-1. Provide a name for the request. A default value is entered based on the request details, but you can update the value.
-1. Optionally choose a folder to save the request under.
-1. Click Save
-
-The saved request is created and should appear in the left rail of the screen.
+1. A dialog appears with form fields.
+1. Provide a name for the request. A default value is provided based on the request details, but you can update the value.
+    ![Save request dialog](./media/api-play-save.svg)
+1. Click **Save**
+1. The saved request appears in the left rail of the screen.
+    ![Saved requests appear in the left rail of the screen](media/api-play-saved-requests.svg)
 
 ### Load a saved request
 
-Saved requests are displayed in the left rail of any screen. You can only view saved requests that you have created.
-
-To load a saved request, simply select a request name by clicking on the list item. This will load the request screen with the request details filled in.
-
-### Create a folder
+To load a saved request, select a request name. This will load the request screen with the request details filled in, including input parameters and values.
 
-Use folders to manage saved requests into groups.
-
-1. In the left rail, click the + (new) button > Create folder
-1. In the dialog that appears, provide a name for the folder
-1. Click save
+> [!NOTE]
+> You can only view saved requests that you have created.
 
 ## FAQs
 
@@ -151,16 +147,12 @@ Yes, the API playground tool only connects to the Dataverse Web API. No other se
 
 ### How does the API playground tool authenticate to the Dataverse Web API?
 
-The tool uses the auth token of the logged in user via the Power Platform framework, which is required for playing any application in Power Apps.
+The tool uses the authentication token of the logged in user that was required to play the Dataverse accelerator application.
 
 ### Is the API playround feature available in all environments?
 
 The feature is delivered through the Dataverse accelerator and is available in all environments that have the app installed. The app is automatically installed in all new environments, but can also be installed in older environments by following the [install instructions](dataverse-accelerator.md#install-the-dataverse-accelerator).
 
-### How do I update or delete folders?
-
-Use the table explorer to manage folders as rows in the **API Request Folder** table in the maker portal (make.powerapps.com). We will provide in-app experiences to manage the folders in subsequent updates.
-
 ## See also
 
 [Get preview features early with the Dataverse accelerator (preview)](dataverse-accelerator.md)

powerapps-docs/maker/data-platform/dataverse-accelerator/dataverse-accelerator.md

@@ -58,7 +58,8 @@ You must have the following privileges in your Dataverse environment:
 | Feature | Description |
 | -- | -- |
 | [Low-code plug-ins](../low-code-plug-ins.md) | Reusable, real-time workflows that execute a specific set of commands within Dataverse. Low-code plug-ins run server-side and are triggered by personalized event handlers, defined in Power Fx. |
-| [Plug-in monitoring](plugin-monitoring.md) | A modern interface to surface the existing plug-in trace log table in Dataverse environments, designed for developing and debugging Dataverse plug-ins and custom APIs.  |
+| [Plug-in monitor](plugin-monitoring.md) | A modern interface to surface the existing plug-in trace log table in Dataverse environments, designed for developing and debugging Dataverse plug-ins and custom APIs.  |
+| [API playground](api-playground.md) | a pre-authenticated software testing tool that helps makers quickly and conveniently interact with the [Microsoft Dataverse Web API](/power-apps/developer/data-platform/webapi/overview). |
 
 ## Manage the Dataverse accelerator app