- 
+3. This default channel `/*` will have a default operation `receive_/*`.
- 2. Select **sub** under **Types**, enter the **Topic Name**, and click **+** as shown below, to add a new topic.
+ 
- 
+4. Modify the topics as follows and click **Save** to update them.
- The newly added topic is displayed as follows.
+ 1. Optionally, click delete as shown below, to delete an existing topic or an operation.
- 
+ 
+
+ 2. Select **receive** under **Types**, enter the **Address** of the channel to be created, enter the **Operation Name** to be added to the selected channel, and click **+** as shown below, to add a new topic.
+
+ 
+
+ The newly added topic is displayed as follows. Expand the topic to view the newly added operation.
+
+ 
+
+ 3. You can also add a new operation to an existing topic by selecting the respective channel address from the dropdown.
+
+ 
+
+ Expand the topic to view the newly added operation.
+
+ 
### Step 3 - View the AsyncAPI Definition
Click **AsyncAPI Definition** under **API Configurations**.
+!!! note
+ The API definition will be generated in AsyncAPI V3.0.0.
+
The AsyncAPI definition of the streaming API, which you just created, appears.
-
+
### Step 4 - Configure the Runtime Configurations
diff --git a/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-streaming-api-from-an-asyncapi-definition.md b/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-streaming-api-from-an-asyncapi-definition.md
index 505a72262e..660f48b05c 100644
--- a/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-streaming-api-from-an-asyncapi-definition.md
+++ b/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-streaming-api-from-an-asyncapi-definition.md
@@ -29,15 +29,19 @@ Follow the instructions below to create a Streaming API using an AsyncAPI defini
* **AsyncAPI URL** - If you select this option, you need to provide a URL.
* **AsyncAPI File** - If you select this option, click **Browse File to Upload** and upload a file, which contains an AsyncAPI definition.
-3. Select the way in which you are going to import the AsynAPI definition, and click **Next**.
-
- For this example, let's select **AsyncAPI URL**, provide the following URL, and click **Next**.
+3. Select the way in which you are going to import the AsyncAPI definition, and click **Next**.
- ```sh
- https://raw.githubusercontent.com/asyncapi/spec/v2.0.0/examples/2.0.0/streetlights.yml
- ```
+ Note
+AsyncAPI import now supports both AsyncAPI v2.x and AsyncAPI v3.0 definitions.
+
+ [Download AsyncAPI V3 file]({{base_path}}/assets/attachments/103332601/streetlights_v3-def.yml)
+
+ 
4. Edit the Streaming API information and click **Create**.
@@ -67,19 +71,25 @@ Follow the instructions below to create a Streaming API using an AsyncAPI defini
Click **Topics** to navigate to the topics page.
-[]({{base_path}}/assets/img/design/create-api/streaming-api/websocket-streaming-api-from-asyncapi-topics.png)
+[]({{base_path}}/assets/img/design/create-api/streaming-api/asyncv3-topics.png)
You will notice that the topics have been created automatically from the AsyncAPI definition specified in the provided URL.
+[]({{base_path}}/assets/img/design/create-api/streaming-api/asyncv3-operations.png)
+
+Expand each topic to view the operations which are automatically created for each channel, as defined in the specification.
+
## Step 3 - View the AsyncAPI Definition
Click **AsyncAPI Definition** under **API Configurations**.
The AsyncAPI definition of the streaming API, which you just created, appears.
- 
+ 
+
+Now, you have successfully created a Streaming API from an Async API Definition.
-Now, you have successfully created a Streaming API from an Async API Definition.
+If you have created the streaming API using an AsyncAPI v2.x definition, see [AsyncAPI v2.x for APIM 4.6.0](https://apim.docs.wso2.com/en/latest/api-design-manage/design/create-api/create-streaming-api/create-a-streaming-api-from-an-asyncapi-definition/).
Next, publish the API, for more information, see [Publish an API]({{base_path}}/deploy-and-publish/publish-on-dev-portal/publish-an-api).
diff --git a/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-websocket-streaming-api.md b/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-websocket-streaming-api.md
index 47cb623d4f..cc9b790a55 100644
--- a/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-websocket-streaming-api.md
+++ b/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-websocket-streaming-api.md
@@ -129,44 +129,66 @@ Follow the instructions below to create a WebSocket API using the basic flow:
### Step 2 - Configure the Topics
-Topics of a WebSocket API are always **Subscribe (sub) and Publish (pub)**, where the flow of events can be either from the server (backend) to the clients or from the client to the server. By default, the WebSocket API will have a topic with the name `/*`.
+Topics of a WebSocket API represents the channels which support actions **Receive and Send**, where the flow of events can be either from the server (backend) to the clients or from the client to the server.
1. Click **Topics** under **API Configurations** and navigate to the **Topics** page.
+
+2. By default, the newly created WebSocket API will have a topic with the name `/*`.
-2. Modify the topics as follows and click **Save** to update them.
+ 
- 1. Optionally, click delete as shown below, to delete an existing topic.
+3. This default channel `/*` will have two default operations `send_/*` and `receive_/*` and are listed inside the respective action of the channel.
- 
+ 
- 2. Select the **Types**, enter the **Topic Name**, and click **+** as shown below, to add a new topic.
+4. Modify the topics as follows and click **Save** to update them.
- | Topic Name | /notifications |
+ 
- The newly added topic is displayed as follows.
+ 2. Select a **Type**, enter the **Address** of the channel to be created, enter the **Operation Name** to be added to the selected channel, and click **+** as shown below, to add a new topic.
- 
+ | Channel Address | /notifications |
| Operation Name | sendNotifications |
+
+ The newly added topic is displayed as follows. Expand the topic to view the newly added operation.
+
+ 
+
+ 3. You can also add a new operation to an existing topic by selecting the respective channel address from the dropdown.
+
+ 
+
+ Expand the topic to view the newly added operation.
+
+ 
+
+ 4. Optionally, provide a URL Mapping to the topic.
The provided URL Mapping will be appended to the WebSocket endpoint URL that you provided when creating the API, and the traffic via this topic will be sent to the resulting URL.
- Expand **both** PUB and SUB under the created topic, provide the same URL Mapping for both and click **Save**.
+ Expand **both** SEND and RECEIVE under the created topic, provide the same URL Mapping for both and click **Save**.
| Description | Chat room notifications |
| URL Mapping | /notifications |
+ 
### Step 3 - View the AsyncAPI Definition
Click **AsyncAPI Definition** under **API Configurations**.
+!!! note
+ The API definition will be generated in AsyncAPI V3.0.0.
+
The AsyncAPI definition of the streaming API, which you just created, appears.
- 
+ 
### Step 4 - Configure the Runtime Configurations
diff --git a/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-websub-streaming-api.md b/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-websub-streaming-api.md
index e8c599ce5d..4f1631c90f 100644
--- a/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-websub-streaming-api.md
+++ b/en/docs/api-design-manage/design/create-api/create-streaming-api/create-a-websub-streaming-api.md
@@ -73,33 +73,52 @@ Follow the instructions below to create a WebHook API using the basic flow:
### Step 2 - Configure the Topics
-Topics of a WebSub/Webhook API are always **Subscribe only**. By default, a WebSub/Webhook API will have a topic with the name `_default`.
+Topics of a WebSub/Webhook API are always **Receive only**.
1. Click **Topics** under **API Configurations** to navigate to the **Topics** page.
-2. Modify the topics as follows and click **Save** to update them.
+2. By default, the newly created WebSub/Webhook API will have a topic with the name `_default`.
- 1. Optionally, click delete, as shown below, to delete an existing topic.
+ 
- 
+3. This default channel `_default` will have a default operation `receive__edfault`.
- 2. Select **sub** under **Types**, enter the **Topic Name**, and click **+** as shown below, to add a new topic.
+ 
- 
+4. Modify the topics as follows and click **Save** to update them.
- The newly added topic is displayed as follows.
+ 1. Optionally, click delete as shown below, to delete an existing topic or an operation.
- 
+ 
+
+ 2. Select **receive** under **Types**, enter the **Address** of the channel to be created, enter the **Operation Name** to be added to the selected channel, and click **+** as shown below, to add a new topic.
+
+ 
+
+ The newly added topic is displayed as follows. Expand the topic to view the newly added operation.
+
+ 
Expand the created topic to view its **Callback URL**. You can use this when registering the topic with a WebHook provider (WebSub Provider).
+ 3. You can also add a new operation to an existing topic by selecting the respective channel address from the dropdown.
+
+ 
+
+ Expand the topic to view the newly added operation.
+
+ 
+
### Step 3 - View the AsyncAPI Definition
Click **AsyncAPI Definition** under **API Configurations**.
+!!! note
+ The API definition will be generated in AsyncAPI V3.0.0.
+
The AsyncAPI definition of the streaming API, which you just created, appears.
- 
+ 
### Step 4 - Configure the Runtime Configurations
diff --git a/en/docs/api-developer-portal/invoke-apis/invoke-apis-using-tools/invoke-an-api-using-a-soap-client.md b/en/docs/api-developer-portal/invoke-apis/invoke-apis-using-tools/invoke-an-api-using-a-soap-client.md
index e9d9952e65..073dade2f9 100644
--- a/en/docs/api-developer-portal/invoke-apis/invoke-apis-using-tools/invoke-an-api-using-a-soap-client.md
+++ b/en/docs/api-developer-portal/invoke-apis/invoke-apis-using-tools/invoke-an-api-using-a-soap-client.md
@@ -27,10 +27,15 @@ Let's invoke the `PhoneVerification` API using a SOAP client.
[]({{base_path}}/assets/attachments/103332601/soap-ui-new-project.png)
-8. Give your API's WSDL and click **OK**.
- In this case, the WSDL is as follows: Note: In distributed or high-availability deployments, all API-M instances must use the same symmetric encryption key. Ensure the identical key value is added to the deployment.toml of every node in the cluster to maintain the ability to decrypt registry resources across instances.
Generate a random string and add it to the deployment.toml file. See Configure WSDL URL generation secret
+ for instructions.
Note: In distributed or high-availability deployments, all API-M instances must use the same secret key. Ensure the identical key value is added to the deployment.toml of every node in the cluster to maintain the ability to validate generated WSDL URLs across instances.
Configure WSDL URL generation secret
+If you are using the WSDL URL of a SOAP API generated using the Developer Portal,
+configure a secret to secure the generated URLs. Add the following to
+the deployment.toml file:
+
+
+[apim.devportal]
+url_generation_secret = "your_secret"
+
+
++A randomly generated string of at least 32 characters is recommended. You can generate a strong secret using the following command: +
+openssl rand -base64 32+It is highly recommended to encrypt this secret using the secure vault. See Encrypting Passwords in Configuration Files for instructions. +
+| Type | Channel Address | Operation |
|---|---|---|
| send | /notifications | sendNotifications |
| receive | /notifications | receiveNotifications |
| send | /rooms/{roomID} | sendMessages |
| receive | /rooms/{roomID} | receiveMessages |
+ 
4. Expand each topic, provide URL Mappings as follows, and click **Save**.
@@ -103,7 +106,7 @@ This will demonstrate a simple command line based chat room which has two channe
URL Mapping provided for a topic will be appended to the WebSocket endpoint URL, which was provided when creating the API, and the traffic via the topic will be sent to & received from the resulting URL.
- []({{base_path}}/assets/img/tutorials/streaming-api/websocket-api-topic-url-mapping.png)
+ []({{base_path}}/assets/img/tutorials/streaming-api/websocket-api-v3-topic-url-mapping.png)
6. Attach business plans to your WebSocket API.
diff --git a/en/docs/tutorials/streaming-api/create-and-publish-websub-api.md b/en/docs/tutorials/streaming-api/create-and-publish-websub-api.md
index 48fce479d8..6fec2937f1 100644
--- a/en/docs/tutorials/streaming-api/create-and-publish-websub-api.md
+++ b/en/docs/tutorials/streaming-api/create-and-publish-websub-api.md
@@ -61,13 +61,13 @@ The tutorial demonstrates a simple WebSub/WebHook API that monitors your GitHub
2. Click **Add Topic**, add a topic with the name **/issues**, click **Add**, and finally click **Save**.
- []({{base_path}}/assets/img/tutorials/streaming-api/websub-api-add-topic.png)
+ []({{base_path}}/assets/img/design/create-api/streaming-api/websub-api-v3-add-topic.png)
6. Generate a secret.
1. Expand the **Subscription Configuration** section in the **Topics** page.
- []({{base_path}}/assets/img/tutorials/streaming-api/enable-secret-generation.png)
+ []({{base_path}}/assets/img/tutorials/streaming-api/enable-secret-generation-v3.png)
2. Click **Enable** to enable secret generation.