[API Shield] Various updates

public/__redirects

@@ -210,6 +210,7 @@
 # api-shield
 /api-shield/security/sequential-abuse-detection/ /api-shield/security/sequence-analytics/ 301
 /api-shield/security/bola-attack-detection/ /api-shield/security/bola-vulnerability-detection/ 301
+/api-shield/management-and-monitoring/api-routing/configure/ /api-shield/management-and-monitoring/api-routing/ 301
 
 #autorag
 /autorag/usage/recipes/ /autorag/how-to/ 301

src/content/docs/api-shield/security/sequence-analytics.mdx

@@ -26,7 +26,7 @@ For example, a portion of a sequence made during a bank funds transfer could loo
 | 3     | `GET`  | `/api/v1/accounts/{account_id}/balance` | `account_id` is a different account belonging to the user.                                                                                     |
 | 4     | `POST` | `/api/v1/transferFunds`                 | This contains a request body detailing an account to transfer funds from, an account to transfer funds to, and an amount of money to transfer. |
 
-API Shield uses your configured <GlossaryTooltip term="session identifier">session identifier</GlossaryTooltip> to build a set of ordered API operations (HTTP host, method, and path) requested per session. We may surface sequences in various lengths depending how API Shield scores the sequences.
+API Shield uses your configured <GlossaryTooltip term="session identifier">session identifier</GlossaryTooltip> and your saved endpoints to build a set of ordered API operations (HTTP host, method, and path) requested per session. We may surface sequences in various lengths depending how API Shield scores the sequences.
 
 ### Sequence scoring
 
@@ -54,6 +54,6 @@ Sequence Analytics is available for all API Shield customers. Pro, Business, and
 
 ## Limitations
 
-Sequence Analytics currently requires a session identifier in order to build and track sequences made by an API consumer. Ensure that you have set up your session identifier(s) in the Cloudflare dashboard by going to **API Shield** > **Settings**.
+Sequence Analytics currently requires a session identifier and saved endpoints in order to build and track sequences made by an API consumer. Ensure that you have [set up your session identifier(s)](/api-shield/get-started/#session-identifiers) and [saved your endpoints](/api-shield/management-and-monitoring/endpoint-management/).
 
 Sequences are currently limited to nine operations in length.

src/content/docs/api-shield/security/sequence-mitigation/custom-rules.mdx

@@ -12,7 +12,7 @@ API Shield sequence custom rules use the configured API Shield <GlossaryTooltip
 
 These rules are different from [cookie sequence rules](/bots/additional-configurations/sequence-rules/) in a few ways: 
 
-- They only require an API Shield subscription.
+- They need the `fraud_acct_ent` entitlement on a Cloudflare account.
 - They require [session identifiers](/api-shield/get-started/#session-identifiers) to be set in API Shield.
 - Because they use an API's session identifiers, they can be used for APIs designed for mobile applications.
 - Because Cloudflare stores the user state in memory and not in a cookie, the session lifetime is limited to 10 minutes.