diff --git a/modules/ROOT/pages/_partials/task-add-api-instance.adoc b/modules/ROOT/pages/_partials/task-add-api-instance.adoc
index c31f70d6..b2e0b8d7 100644
--- a/modules/ROOT/pages/_partials/task-add-api-instance.adoc
+++ b/modules/ROOT/pages/_partials/task-add-api-instance.adoc
@@ -135,10 +135,13 @@ For more information about versions in Exchange, see xref:exchange::asset-versio
 ** **REST API:** Select this option if you have a RAML or OAS API definition file you want to include for your asset.
 +
 Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are the recommended versions for OAS or RAML specs, because these versions add native OAS support. If you upload an OAS API specification to an API proxy version 1.0 or earlier, your API specification is translated to RAML.
-** **HTTP API:** Select this option if you do not have an API definition file you want to include for your asset.
+** **HTTP API:** Select this option if you do not have an API definition file you want to include for your asset. For WebSocket APIs, select HTTP and then choose the WebSocket subtype when selecting the API from Exchange. WebSocket instances can use HTTP or AsyncAPI assets from Exchange.
 ** **SOAP API:** Select this option if you have a WSDL API definition file or an external link to the file.
 +
 Upload a WSDL file for your SOAP API or add the link to the file.
+** **GraphQL API:** Select this option if you have a GraphQL schema definition file you want to include for your asset.
++
+Upload the GraphQL schema definition for your GraphQL API.
 
 .. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
 +
@@ -154,10 +157,13 @@ For more information about versions in Exchange, see xref:exchange::asset-versio
 ** **REST API:** Select this option if you have a RAML or OAS API definition file you want to include for your asset.
 +
 Upload either a RAML or OAS file for your REST API. Versions 2.0.0 and later are the recommended versions for OAS or RAML specs, because these versions add native OAS support. If you upload an OAS API specification to an API proxy version 1.0 or earlier, your API specification is translated to RAML.
-** **HTTP API:** Select this option if you do not have an API definition file you want to include for your asset.
+** **HTTP API:** Select this option if you do not have an API definition file you want to include for your asset. For WebSocket APIs, select HTTP and then choose the WebSocket subtype when selecting the API from Exchange. WebSocket instances can use HTTP or AsyncAPI assets from Exchange.
 ** **SOAP API:** Select this option if you have a WSDL API definition file or an external link to the file.
 +
 Upload a WSDL file for your SOAP API or add the link to the file.
+** **GraphQL API:** Select this option if you have a GraphQL schema definition file you want to include for your asset.
++
+Upload the GraphQL schema definition for your GraphQL API.
 
 .. Update the *Asset type*, *API version*, and *Asset version* if you are not using the latest version.
 +
diff --git a/modules/ROOT/pages/getting-started-proxy.adoc b/modules/ROOT/pages/getting-started-proxy.adoc
index 20bac415..a418c540 100644
--- a/modules/ROOT/pages/getting-started-proxy.adoc
+++ b/modules/ROOT/pages/getting-started-proxy.adoc
@@ -13,7 +13,7 @@ You can manage your instance using the following steps:
 
 . xref:exchange::to-create-an-asset.adoc#create-an-api-asset[Create an API asset in Exchange]
 +
-You can create a REST, HTTP, SOAP, or gRPC API asset in Exchange and manage it as an API instance
+You can create a REST, HTTP (including the WebSocket subtype), AsyncAPI, SOAP, gRPC, or GraphQL API asset in Exchange and manage it as an API instance
 in API Manager.
 . xref:create-instance-task.adoc[Add an API Instance in API Manager]
 +