fix broken links.

dushaniw · dushaniw · commit 1f0db38b46d9 · 2025-12-10T12:35:37.000+05:30
diff --git a/en/docs/api-gateway/api-gateways-with-dedicated-backends.md b/en/docs/api-gateway/api-gateways-with-dedicated-backends.md
@@ -1,6 +1,6 @@
 # Gateways with Dedicated Backends
 
-We can extend the [multiple gateway environments]({{base_path}}/manage-apis/deploy-and-publish/api-gateway/maintaining-separate-production-and-sandbox-gateways) feature by utilizing parameterized endpoint capabilities of WSO2 API Manager to have each gateway point to a different back-end endpoint. Universal Gateway is the actual runtime of the APIs that are developed and published from the API Publisher. WSO2 API Manager is capable of publishing APIs to different Gateways where API users connect to those Universal Gateways in order to do the actual API calls through the applications to which they are subscribed.
+We can extend the [multiple gateway environments]({{base_path}}/api-gateway/maintaining-separate-production-and-sandbox-gateways) feature by utilizing parameterized endpoint capabilities of WSO2 API Manager to have each gateway point to a different back-end endpoint. Universal Gateway is the actual runtime of the APIs that are developed and published from the API Publisher. WSO2 API Manager is capable of publishing APIs to different Gateways where API users connect to those Universal Gateways in order to do the actual API calls through the applications to which they are subscribed.
 
 However, the API Publisher can only provide a single static endpoint for an API in the implementation. Therefore, the API call is directed to a single endpoint in whichever Gateway the API is deployed in, as depicted in the diagram below.
 
@@ -18,7 +18,7 @@ Follow the steps below to configure a parameterized endpoint as the API endpoint
 
     [![Dedicated backend definition]({{base_path}}/assets/img/learn/dedicated-backend-def.png)]({{base_path}}/assets/img/learn/dedicated-backend-def.png)
 
-3.  Save and [publish]({{base_path}}/manage-apis/deploy-and-publish/publish-on-dev-portal/publish-an-api) the API.
+3.  Save and [publish]({{base_path}}/api-design-manage/deploy-and-publish/publish-on-dev-portal/publish-an-api) the API.
 
 4.  Navigate to the `<API-M_HOME>/repository/deployment/server/synapse-configs/default/sequences` directory of each Gateway and create the following sequence.
 
diff --git a/en/docs/api-gateway/federated-gateways/aws/deploy-on-aws-api-gateway.md b/en/docs/api-gateway/federated-gateways/aws/deploy-on-aws-api-gateway.md
@@ -43,7 +43,7 @@ Follow the instructions given below to configure AWS API Gateway as a Federated
 
     `https://localhost:9443/admin`
 
-2. Register a third party KM following instructions in WSO2 documentation. In this guide we will setup Auth0 as the KM following the guide [Configure Auth0 as a Key Manager]({{base_path}}/administer/key-managers/configure-auth0-connector/).
+2. Register a third party KM following instructions in WSO2 documentation. In this guide we will setup Auth0 as the KM following the guide [Configure Auth0 as a Key Manager]({{base_path}}/api-security/key-management/third-party-key-managers/configure-auth0-connector/).
 
 ## Step 4 : Create and Design API
 
diff --git a/en/docs/api-gateway/federated-gateways/overview.md b/en/docs/api-gateway/federated-gateways/overview.md
@@ -29,7 +29,7 @@ Deploy and manage APIs on Amazon Web Services API Gateway. WSO2 API Manager come
 - OAuth 2.0 security via Lambda Authorizer
 - Centralized management through WSO2 API Manager
 
-[Learn more about AWS API Gateway deployment]({{base_path}}/manage-apis/deploy-and-publish/federated-gateways/aws/deploy-on-aws-api-gateway/)
+[Learn more about AWS API Gateway deployment]({{base_path}}/api-gateway/federated-gateways/aws/deploy-on-aws-api-gateway/)
 
 ### Azure API Gateway
 Deploy and manage APIs on Microsoft Azure API Management Service. The built-in Azure gateway connector facilitates deployment and discovery of APIs on Azure infrastructure.
@@ -51,7 +51,7 @@ Discover and manage APIs deployed on Kong Gateway. WSO2 API Manager supports bot
 - Support for Kong Kubernetes and Standalone modes
 - Unified management through WSO2 API Manager Control Plane
 
-[Learn more about Kong Gateway integration]({{base_path}}/manage-apis/deploy-and-publish/federated-gateways/kong/kong-standalone/discover-apis-on-kong-gateway/)
+[Learn more about Kong Gateway integration]({{base_path}}/api-gateway/federated-gateways/kong/kong-standalone/discover-apis-on-kong-gateway/)
 
 ### Envoy Gateway
 Discover and manage APIs deployed on Envoy Gateway in Kubernetes environments. 
@@ -61,7 +61,7 @@ Discover and manage APIs deployed on Envoy Gateway in Kubernetes environments.
 - Kubernetes-native integration
 - Centralized API governance
 
-[Learn more about Envoy Gateway integration]({{base_path}}/manage-apis/deploy-and-publish/federated-gateways/EnvoyGateway/eg-k8s/discover-apis-on-eg-gateway-in-kubernetes/)
+[Learn more about Envoy Gateway integration]({{base_path}}/api-gateway/federated-gateways/EnvoyGateway/eg-k8s/discover-apis-on-eg-gateway-in-kubernetes/)
 
 ## Gateway Modes
 
@@ -75,7 +75,7 @@ Federated gateways can operate in different modes depending on your requirements
 
 If you need to integrate with a third-party gateway that is not supported out-of-the-box, WSO2 API Manager provides the flexibility to create custom gateway agents. This allows you to extend the federated gateway capabilities to any external gateway.
 
-[Learn more about configuring custom gateway agents]({{base_path}}/manage-apis/deploy-and-publish/federated-gateways/configure-custom-gateway-agent/)
+[Learn more about configuring custom gateway agents]({{base_path}}/api-gateway/federated-gateways/configure-custom-gateway-agent/)
 
 ## Architecture Benefits
 
diff --git a/en/docs/api-gateway/gateway-policies.md b/en/docs/api-gateway/gateway-policies.md
@@ -55,7 +55,7 @@ Follow the instructions provided below to create a gateway policy:
         [![Save individual policy data]({{base_path}}/assets/img/deploy/gateway/global-polices-add-header-policy.png){: style="width:90%"}]({{base_path}}/assets/img/deploy/gateway/global-polices-add-header-policy.png)
 
         !!!note
-            All the policies listed for addition as global policies are [common policies]({{base_path}}/manage-apis/design/api-policies/create-policy/).
+            All the policies listed for addition as global policies are [common policies]({{base_path}}/api-design-manage/design/api-policies/create-policy/).
 
     5. After saving the dropped policy, you should now be able to view the associated **Add Header** policy indicated by the initials **AH**.
 
@@ -95,4 +95,4 @@ To undeploy a global policy from any gateway environment, simply click on the cl
 
 You can engage policies with APIs and their resources:
 
-[Attaching API Policies]({{base_path}}/manage-apis/design/api-policies/attach-policy/)
+[Attaching API Policies]({{base_path}}/api-design-manage/design/api-policies/attach-policy/)
diff --git a/en/docs/api-gateway/mutual-ssl-between-api-gateway-and-backend.md b/en/docs/api-gateway/mutual-ssl-between-api-gateway-and-backend.md
@@ -110,7 +110,7 @@ Now both the backend service and API Manager are configured to use default key s
 
 You can do the following to test your mutual SSL configurations
 
-1.  [Create an API]({{base_path}}/manage-apis/design/create-api/create-rest-api/create-a-rest-api)
-2.  [Publish the API]({{base_path}}/manage-apis/deploy-and-publish/publish-on-dev-portal/publish-an-api)
-3.  [Subscribe to the API]({{base_path}}/consume/manage-subscription/subscribe-to-an-api)
-4.  [Invoke the API]({{base_path}}/consume/invoke-apis/invoke-apis-using-tools/invoke-an-api-using-the-integrated-api-console)
+1.  [Create an API]({{base_path}}/api-design-manage/design/create-api/create-rest-api/create-a-rest-api)
+2.  [Publish the API]({{base_path}}/api-design-manage/deploy-and-publish/publish-on-dev-portal/publish-an-api)
+3.  [Subscribe to the API]({{base_path}}/api-developer-portal/manage-subscription/subscribe-to-an-api)
+4.  [Invoke the API]({{base_path}}/api-developer-portal/invoke-apis/invoke-apis-using-tools/invoke-an-api-using-the-integrated-api-console)
diff --git a/en/docs/api-gateway/policies/adding-a-class-mediator.md b/en/docs/api-gateway/policies/adding-a-class-mediator.md
@@ -55,7 +55,7 @@ public class SimpleClassMediator extends AbstractMediator {
 
 Then we can export this class as a jar file and add as a library to `<API-M_HOME>/repository/components/lib` directory.
 
-By referring to this class with the fully qualified class name in a class mediator, we can create a new policy. Considering the below file content structure, you can create your own content and save as a `.xml` file. We will make use of this `.xml` file (i.e. policy file) when creating the policy (refer to [Create a Policy]({{base_path}}/manage-apis/design/api-policies/create-policy/) for further details). Thus created policy can then be attached to either the request flow or response flow of any API operation (refer [Attach Policies]({{base_path}}/manage-apis/design/api-policies/attach-policy/) for further details).
+By referring to this class with the fully qualified class name in a class mediator, we can create a new policy. Considering the below file content structure, you can create your own content and save as a `.xml` file. We will make use of this `.xml` file (i.e. policy file) when creating the policy (refer to [Create a Policy]({{base_path}}/api-design-manage/design/api-policies/create-policy/) for further details). Thus created policy can then be attached to either the request flow or response flow of any API operation (refer [Attach Policies]({{base_path}}/api-design-manage/design/api-policies/attach-policy/) for further details).
 
 !!! example
     ```xml
diff --git a/en/docs/api-gateway/policies/adding-a-non-blocking-send-operation.md b/en/docs/api-gateway/policies/adding-a-non-blocking-send-operation.md
@@ -21,4 +21,4 @@ Let's create a new policy using the example provided below. Go ahead and create
     </sequence>
     ```
 
-Let's assume that the policy file that you created by considering the example above is `addNonBlockingSend.xml`. We will next create a policy using this policy file. You can refer to [Create a Policy]({{base_path}}/manage-apis/design/api-policies/create-policy/) to learn more about how to achieve this. When creating the policy, make sure to only select the `Request` flow when filling out the general details of the create policy form. Thus created policy can then be attached to the request flow of any API operation (refer [Attach Policies]({{base_path}}/manage-apis/design/api-policies/attach-policy/) for further details).
+Let's assume that the policy file that you created by considering the example above is `addNonBlockingSend.xml`. We will next create a policy using this policy file. You can refer to [Create a Policy]({{base_path}}/api-design-manage/design/api-policies/create-policy/) to learn more about how to achieve this. When creating the policy, make sure to only select the `Request` flow when filling out the general details of the create policy form. Thus created policy can then be attached to the request flow of any API operation (refer [Attach Policies]({{base_path}}/api-design-manage/design/api-policies/attach-policy/) for further details).
diff --git a/en/docs/api-gateway/policies/passing-a-custom-authorization-token-to-the-backend.md b/en/docs/api-gateway/policies/passing-a-custom-authorization-token-to-the-backend.md
@@ -26,7 +26,7 @@ Here's a summary:
         </sequence>
         ```
 
-2.  Log in to the **API Publisher**, create a new REST API with the information given in the table below by following the instructions in [Create a REST API]({{base_path}}/manage-apis/design/create-api/create-rest-api/create-a-rest-api/).
+2.  Log in to the **API Publisher**, create a new REST API with the information given in the table below by following the instructions in [Create a REST API]({{base_path}}/api-design-manage/design/create-api/create-rest-api/create-a-rest-api/).
 
     | Field         | Sample Value         |
     |---------------|----------------------|
@@ -35,7 +35,7 @@ Here's a summary:
     | Version       | 1.0.0                |
     | Endpoint      | http://wso2cloud-custom-auth-header-sample-1-0-0.wso2apps.com/custom-auth-header/validate-header |
 
-3.  Navigate to the **API Configurations** --> **Policies** tab. Create a new policy with the information given in the table below by following the instructions in [Create a Policy]({{base_path}}/manage-apis/design/api-policies/create-policy/).
+3.  Navigate to the **API Configurations** --> **Policies** tab. Create a new policy with the information given in the table below by following the instructions in [Create a Policy]({{base_path}}/api-design-manage/design/api-policies/create-policy/).
 
     | Section                   | Field             | Sample Value          |
     |---------------------------|-------------------|-----------------------|
@@ -47,7 +47,7 @@ Here's a summary:
     | Gateway Specific Details  | Policy File       | `tokenExchange.xml` file you created |
     | Policy Attributes         | N/A               | N/A                     |
 
-4.  Next, find the **Custom Authorization Token** policy that you just created by following Step 3, from the `Request` tab of the policy list. Drag and drop this policy to the desired API operation(s) by following the instructions in [Attach Policies]({{base_path}}/manage-apis/design/api-policies/attach-policy/).
+4.  Next, find the **Custom Authorization Token** policy that you just created by following Step 3, from the `Request` tab of the policy list. Drag and drop this policy to the desired API operation(s) by following the instructions in [Attach Policies]({{base_path}}/api-design-manage/design/api-policies/attach-policy/).
 
     [![Custom Authorization Token Policy]({{base_path}}/assets/img/design/api-policies/custom-authorization-token-policy.png)]({{base_path}}/assets/img/design/api-policies/custom-authorization-token-policy.png)
 
@@ -60,7 +60,7 @@ Here's a summary:
 5. Go to the **Developer Portal**, subscribe and obtain a token to invoke the published API. 
 
     !!! tip
-        Follow the instructions in [here]({{base_path}}/consume/manage-application/generate-keys/generate-api-keys/#generating-application-keys) to generate an application access token.  
+        Follow the instructions in [here]({{base_path}}/api-developer-portal/manage-application/generate-keys/generate-api-keys/#generating-application-keys) to generate an application access token.  
 
 6. Install any REST client in your machine. We use [cURL](http://curl.haxx.se/download.html) here.
 
diff --git a/en/docs/api-gateway/policies/removing-specific-request-headers-from-response.md b/en/docs/api-gateway/policies/removing-specific-request-headers-from-response.md
@@ -14,7 +14,7 @@ To remove request headers from responses for per API or globally, add the name o
         ``` bash
         <property name="CustomTransportHeader" scope="transport" action="remove"/>
         ```
-Check out [Changing the Default Mediation Flow of API Requests]({{base_path}}/manage-apis/deploy-and-publish/deploy-on-gateway/api-gateway/message-mediation/changing-the-default-mediation-flow-of-api-requests) to learn on how to
+Check out [Changing the Default Mediation Flow of API Requests]({{base_path}}/api-gateway/message-mediation/changing-the-default-mediation-flow-of-api-requests) to learn on how to
 add the above mediation policy per API or globally.
 
 ## Handling Error Responses
diff --git a/en/docs/api-gateway/policies/revoke-one-time-tokens-policy.md b/en/docs/api-gateway/policies/revoke-one-time-tokens-policy.md
@@ -1,6 +1,6 @@
 # Revoke One Time Tokens Policy
 
-The [JWT access tokens]({{base_path}}/manage-apis/design/api-security/oauth2/access-token-types/jwt-tokens/) issued in the Gateway can be used to access the dedicated API resource as many times as the user needs. However, if the application developer wants to restrict this ability by providing only one chance to access the resource then One Time Token can be used. One Time Token is a JWT that will be revoked after single usage. This feature is **only available for JWT access tokens**.
+The [JWT access tokens]({{base_path}}/api-security/key-management/tokens/jwt-tokens/) issued in the Gateway can be used to access the dedicated API resource as many times as the user needs. However, if the application developer wants to restrict this ability by providing only one chance to access the resource then One Time Token can be used. One Time Token is a JWT that will be revoked after single usage. This feature is **only available for JWT access tokens**.
 
 ## Workflow
 
@@ -22,14 +22,14 @@ The high level workflow of revocation of One Time Tokens is illustrated below.
 
 ## Enabling One Time Tokens
 
-This feature is only supported for the [Regular Gateway and the Request flow]({{base_path}}/manage-apis/design/api-policies/overview/). In order to enable this feature for the JWTs, two conditions need to be fulfilled.
+This feature is only supported for the [Regular Gateway and the Request flow]({{base_path}}/api-design-manage/design/api-policies/overview/). In order to enable this feature for the JWTs, two conditions need to be fulfilled.
 
 1. Attach the ‘Revoke One Time Token’ policy to the required API resource
 2. Add the relevant scope to the JWT
 
 ### Attach the ‘Revoke One Time Token’ policy
 
-This step can be done by following the steps listed [here]({{base_path}}/manage-apis/design/api-policies/attach-policy/). The below diagram shows which policy to select. You can apply the policy to the whole API or a designated API resource depending on the use case. 
+This step can be done by following the steps listed [here]({{base_path}}/api-design-manage/design/api-policies/attach-policy/). The below diagram shows which policy to select. You can apply the policy to the whole API or a designated API resource depending on the use case. 
 
 The policy has one attribute called scope. If a JWT in your application has the same scope that is mentioned in the policy, it will be identified as a One Time Token. The default value of the scope is “OTT”. However, this can be changed to any name the user prefers.
 
diff --git a/en/docs/api-gateway/policies/transforming-api-message-payload.md b/en/docs/api-gateway/policies/transforming-api-message-payload.md
@@ -14,7 +14,7 @@ from the message. As with message builders, the message formatter is selected ba
     Note that if you edit an API's synapse configuration as mentioned in this guide and then go back to the API 
     Publisher and save the API, your changes will be overwritten. Therefore, we do not recommend changing the API's 
     synapse configuration directly. The recommended way to extend an API's mediation flow is by 
-    [attaching policies to API operations]({{base_path}}/manage-apis/design/api-policies/attach-policy/).
+    [attaching policies to API operations]({{base_path}}/api-design-manage/design/api-policies/attach-policy/).
 
 
 !!! info
diff --git a/en/docs/api-gateway/response-caching.md b/en/docs/api-gateway/response-caching.md
@@ -8,7 +8,7 @@ You need to enable response caching when creating a new API or editing an existi
 
 Please follow below steps to enable response caching for an API.
 
-1.  [Create an API]({{base_path}}/manage-apis/design/create-api/create-rest-api/create-a-rest-api/).
+1.  [Create an API]({{base_path}}/api-design-manage/design/create-api/create-rest-api/create-a-rest-api/).
 
 2.  Navigate to the **Runtime** tab under **API Configurations** where you find the response caching configuration. Then turn on Response caching and give a timeout value. This enables the default response caching settings.
 
diff --git a/en/docs/api-gateway/threat-protectors/gateway-threat-protectors-for-api-manager.md b/en/docs/api-gateway/threat-protectors/gateway-threat-protectors-for-api-manager.md
@@ -2,9 +2,9 @@
 
 WSO2 API Manager has three types of threat protectors for the Gateway.
 
--   [Regular Expression Threat Protection for API Gateway]({{base_path}}/manage-apis/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/regular-expression-threat-protection-for-api-gateway/)
--   [JSON Threat Protection for API Gateway]({{base_path}}/manage-apis/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/json-threat-protection-for-api-gateway/)
--   [XML Threat Protection for API Gateway]({{base_path}}/manage-apis/deploy-and-publish/deploy-on-gateway/api-gateway/threat-protectors/xml-threat-protection-for-api-gateway/)
+-   [Regular Expression Threat Protection for API Gateway]({{base_path}}/api-gateway/threat-protectors/regular-expression-threat-protection-for-api-gateway/)
+-   [JSON Threat Protection for API Gateway]({{base_path}}/api-gateway/threat-protectors/json-threat-protection-for-api-gateway/)
+-   [XML Threat Protection for API Gateway]({{base_path}}/api-gateway/threat-protectors/xml-threat-protection-for-api-gateway/)
 
 ### Combining threat protectors
 
@@ -42,4 +42,4 @@ You can use a combination of the threat protectors given above to validate the m
 ### Add a custom sequence
 
 You can add custom sequences depending on the threats that you need to address. You can create a policy using the custom sequence and attach it to the API. 
-Please refer [API Policies]({{base_path}}/manage-apis/design/api-policies/overview/) for more information on how to attach a policy to an API
+Please refer [API Policies]({{base_path}}/api-design-manage/design/api-policies/overview/) for more information on how to attach a policy to an API
