[Aegis, BYOIP] Use APIRequest component (#22389)

* First pass and placeholder component syntax

* Fill in component props throughout

* Review occurrences and remove old bash codeblock

* Revert service-bindings use for cohesiveness with auth explanation

* Use output highlight for provisioning state

Author: RebeccaTamachiro

src/content/docs/aegis/setup.mdx

@@ -7,6 +7,8 @@ sidebar:
     hideIndex: true
 ---
 
+import { APIRequest } from "~/components";
+
 You can control Aegis enablement on your zones via API. If you are not familiar with how Cloudflare API works, refer to [Fundamentals](/fundamentals/api/).
 
 :::caution[Availability]
@@ -25,12 +27,17 @@ Cloudflare Aegis is available in early access to Enterprise customers. Contact y
 - Specify `aegis` as the setting ID in the URL.
 - In the request body, set `enabled` to `true` and use the ID from the previous step as `pool_id`.
 
-```bash
---data '{
-  "id": "aegis",
-  "value": {
-    "enabled": true,
-    "pool_id": "<YOUR_EGRESS_POOL_ID>"
-  },
-}'
-```
+<APIRequest
+  path="/zones/{zone_id}/settings/{setting_id}"
+  method="PATCH"
+  json={{
+		  "id": "aegis",
+			"value": {
+				"enabled": true,
+				"pool_id": "<YOUR_EGRESS_POOL_ID>",
+				},
+	}}
+	parameters={{
+    setting_id: "aegis",
+  }}
+/>

src/content/docs/byoip/address-maps/setup.mdx

@@ -6,7 +6,7 @@ sidebar:
   label: Setup
 ---
 
-import { GlossaryTooltip } from "~/components";
+import { GlossaryTooltip, APIRequest } from "~/components";
 
 Consider the sections below to learn how to set up address maps.
 
@@ -65,17 +65,14 @@ Default SNI for Spectrum can only be created via API using the [Create Address M
 
 Do not include any membership in your command. Your API command should resemble the following:
 
-```bash
-curl https://api.cloudflare.com/client/v4/accounts/$ACCOUNT_ID/addressing/address_maps \
-  --header "Authorization: Bearer $CLOUDFLARE_API_TOKEN" \
-  --header "Content-Type: application/json" \
-  --data '{
-  "description": "default_sni",
-  "default_sni": "sni.example.com",
-  "enabled": false,
-  "ips": [
-    "192.0.0.1"
-  ],
-  "memberships": []
-}'
-```
+<APIRequest
+  path="/accounts/{account_id}/addressing/address_maps"
+  method="POST"
+  json={{
+		"description": "default_sni",
+		"default_sni": "sni.example.com",
+		"enabled": false,
+		"ips": ["192.0.0.1"],
+		"memberships": [],
+	}}
+/>

src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx

@@ -6,7 +6,7 @@ sidebar:
   label: Magic Transit with CDN
 ---
 
-import { Details, Example, TabItem, Tabs, GlossaryTooltip } from "~/components";
+import { Details, Example, TabItem, Tabs, GlossaryTooltip, APIRequest } from "~/components";
 
 [Magic Transit](/magic-transit/) customers using BYOIP can also benefit from the performance, reliability, and security that Cloudflare offers for HTTP-based applications.
 
@@ -94,24 +94,24 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/addressing/prefi
 --header "Content-Type: application/json" \
 --data '{
   "cidr": "203.0.113.100/32",
-  "service_id": <SERVICE_ID>
+  "service_id": "<SERVICE_ID>"
 }'
 ```
 
 In the response body, the initial provisioning state should be `provisioning`.
 
-```json
+```json output {9}
 {
   "errors": [],
   "messages": [],
   "success": true,
   "result": {
     "cidr": "203.0.113.100/32",
-    "id": <CDN_SERVICE_BINDING_ID>,
+    "id": "<CDN_SERVICE_BINDING_ID>",
     "provisioning": {
       "state": "provisioning"
       },
-    "service_id": <SERVICE_ID>,
+    "service_id": "<SERVICE_ID>",
     "service_name": "CDN"
   }
 }