api shield partials

Author: patriciasantaana

src/content/docs/api-shield/index.mdx

@@ -21,7 +21,14 @@ Identify and address your API vulnerabilities.
 
 ## Why care about API security?
 
-<Render file="why-care" product="api-shield" />
+APIs have become the [backbone of popular web services](https://blog.postman.com/intro-to-apis-history-of-apis/), helping the Internet become more accessible and useful.
+
+As APIs have become more prevalent, however, so have their problems:
+
+* Many companies have [thousands of APIs](/api-shield/security/api-discovery/), including ones they do not even know about.
+* To support a large base of users, many APIs are protected by a negative security model that makes them vulnerable to credential-stuffing attacks and automated scanning tools.
+* With so many endpoints and users, it’s difficult to recognize brute-force attacks against [specific endpoints](/api-shield/security/volumetric-abuse-detection/).
+* Sophisticated attacks are even harder to recognize, often because even development teams are unaware of common and uncommon [usage patterns](/api-shield/security/sequence-analytics/).
 
 Refer to the [Get started](/api-shield/get-started/) guide to set up API Shield.
 

src/content/docs/api-shield/management-and-monitoring/api-routing.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 ---
 
-import { Render, Steps } from "~/components"
+import { Markdown, Render, Steps, Tabs, TabItem } from "~/components"
 
 API Shield Routing enables customers to create a unified external-facing API that routes requests to different back-end services that may have different paths and hosts than the existing zone and DNS configuration.
 
@@ -18,15 +18,62 @@ The term **Source Endpoint** refers to the endpoint managed by API Shield in End
 
 ## Process
 
-<Render file="source-endpoints" />
+
+You must add Source Endpoints to Endpoint Management through established methods, including [uploading a schema](/api-shield/security/schema-validation/#add-validation-by-uploading-a-schema), via [API Discovery](/api-shield/security/api-discovery/), or by [adding manually](/api-shield/management-and-monitoring/#add-endpoints-manually), before creating a route.
+
+To create a route, you will need the operation ID of the Source Endpoint. To find the operation ID in the dashboard:
+
+<Tabs syncKey="dashNewNav">
+    <TabItem label="Old dashboard">
+        <Steps>
+            1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
+            2. Select **Security** > **API Shield**.
+            3. Filter the endpoints to find your **Source Endpoint**.
+            4. Expand the row for your Source Endpoint and note the **operation ID** field.
+            5. Select the copy icon to copy the operation ID to your clipboard.
+        </Steps>
+    </TabItem>
+    <TabItem label="New dashboard" icon="rocket">
+        <Steps>
+            1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
+            2. Select **Security** > **Web assets**.
+            3. Filter the endpoints to find your **Source Endpoint**.
+            4. Expand the row for your Source Endpoint and note the **operation ID** field.
+            5. Select the copy icon to copy the operation ID to your clipboard.
+        </Steps>
+    </TabItem>
+</Tabs>
 
 Once your Source Endpoints are added to Endpoint Management, use the following steps to create and verify routes on any given operation ID:
 
 ### Create a route
 
-<Render file="routing" />
+<Tabs syncKey="dashNewNav">
+    <TabItem label="Old dashboard">
+        <Steps>
+            1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
+            2. Go to **Security** > **API Shield**.
+            3. In **Endpoint Management**, select an existing endpoint and expand its details.
+            4. Under **Routing**, select **Create route**.
+            5. Enter the target URL or IP address to route your endpoint to.
+            6. Select **Deploy route**.
+        </Steps>
+    </TabItem>
+    <TabItem label="New dashboard" icon="rocket">
+        <Steps>
+            1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
+            2. Go to **Security** > **Web assets**.
+            3. In **Endpoints**, select an existing endpoint and expand its details.
+            4. Under **Routing**, select **Create route**.
+            5. Enter the target URL or IP address to route your endpoint to.
+            6. Select **Deploy route**.
+        </Steps>
+    </TabItem>
+</Tabs>
 
-<Render file="routing-path-variables" />
+:::note
+You can reorder path variables if they are present. For example, you can route `/api/{var1}/users/{var2}` to `/{var2}/users/{var1}`. Segments of the path that are not variables may be added or omitted entirely.
+:::
 
 You can also edit or delete a route by selecting **Edit route** on an existing route.
 
@@ -47,4 +94,8 @@ API Shield Routing is currently in an open beta and is only available for Enterp
 
 ## Limitations
 
-<Render file="routing-limitations" />
+The Target Endpoint cannot be routed to a Worker if the route is to the same zone.
+
+You cannot change the method of a request. For example, a `GET` Source Endpoint will always send a `GET` request to the Target Endpoint.
+
+You must use all of the variables in the Target Endpoint that appear in the Source Endpoint. For example, routing `/api/{var1}/users/{var2}` to `/api/users/{var2}` is not allowed and will result in an error since `{var1}` is present in the Source Endpoint but not in the Target Endpoint.

src/content/docs/api-shield/security/api-discovery.mdx

@@ -43,7 +43,7 @@ jp-api.example.com/api/v1/users/{var1}
 
 We will consolidate to `{hostVar1}.example.com/api/v1/users/{var1}`.
 
-<Render file="blog-post" />
+For more technical details, see our [blog post](https://blog.cloudflare.com/ml-api-discovery-and-schema-learning/).
 
 ### Inbox view