Find occurrences and add placeholder syntax throughout

Author: RebeccaTamachiro

src/content/docs/ssl/client-certificates/byo-ca.mdx

@@ -10,7 +10,7 @@ description: Cloudflare mTLS now supports client certificates that have not been
 
 ---
 
-import { Render } from "~/components"
+import { Render, APIRequest } from "~/components"
 
 This page explains how you can manage mTLS using client certificates that have not been issued by Cloudflare CA.
 
@@ -99,4 +99,10 @@ You can also use the [API](/api/resources/certificate_authorities/subresources/h
 curl "https://api.cloudflare.com/client/v4/zones/zone_id/certificate_authorities/hostname_associations?mtls_certificate_id={id_from_step_2}"  \
 --header "X-Auth-Email: <EMAIL>" \
 --header "X-Auth-Key: <API_KEY>"
-```
+```
+
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>

src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/customize-cipher-suites/api.mdx

@@ -6,7 +6,7 @@ sidebar:
   label: Use the API
 ---
 
-import { Render, TabItem, Tabs } from "~/components";
+import { Render, TabItem, Tabs, APIRequest } from "~/components";
 
 <Render file="cipher-suites-definition" />
 
@@ -56,6 +56,13 @@ curl --request PATCH \
 --data '{"value": ["ECDHE-ECDSA-AES128-GCM-SHA256", "ECDHE-ECDSA-CHACHA20-POLY1305", "ECDHE-RSA-AES128-GCM-SHA256", "ECDHE-RSA-CHACHA20-POLY1305", "ECDHE-ECDSA-AES256-GCM-SHA384", "ECDHE-RSA-AES256-GCM-SHA384"]}'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 </TabItem> <TabItem label="compatible">
 
 <Render file="ciphers-api-general-notes" />
@@ -73,6 +80,13 @@ curl --request PATCH \
 --data '{"value": ["ECDHE-ECDSA-AES128-GCM-SHA256", "ECDHE-ECDSA-CHACHA20-POLY1305", "ECDHE-RSA-AES128-GCM-SHA256", "ECDHE-RSA-CHACHA20-POLY1305", "ECDHE-ECDSA-AES256-GCM-SHA384", "ECDHE-RSA-AES256-GCM-SHA384", "ECDHE-ECDSA-AES128-SHA256", "ECDHE-RSA-AES128-SHA256", "ECDHE-ECDSA-AES256-SHA384", "ECDHE-RSA-AES256-SHA384"]}'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 </TabItem> <TabItem label="pci dss">
 
 <Render file="ciphers-api-general-notes" />
@@ -90,6 +104,13 @@ curl --request PATCH \
 --data '{"value": ["ECDHE-ECDSA-AES128-GCM-SHA256", "ECDHE-RSA-AES128-GCM-SHA256", "ECDHE-ECDSA-AES256-GCM-SHA384", "ECDHE-RSA-AES256-GCM-SHA384", "ECDHE-ECDSA-CHACHA20-POLY1305", "ECDHE-RSA-CHACHA20-POLY1305"]}'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 :::caution
 
 For compliance with PCI DSS, also [enable TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/#enable-tls-13) on your zone and make sure to up your [Minimum TLS version](/ssl/edge-certificates/additional-options/minimum-tls/) to `1.2`.
@@ -112,6 +133,13 @@ curl --request PATCH \
 --data '{"value":["AES128-GCM-SHA256", "AES128-SHA", "AES128-SHA256", "AES256-SHA", "AES256-SHA256", "DES-CBC3-SHA", "ECDHE-ECDSA-AES128-GCM-SHA256", "ECDHE-ECDSA-AES128-SHA", "ECDHE-ECDSA-AES128-SHA256", "ECDHE-ECDSA-AES256-GCM-SHA384", "ECDHE-ECDSA-AES256-SHA384", "ECDHE-RSA-AES128-GCM-SHA256", "ECDHE-RSA-AES128-SHA", "ECDHE-RSA-AES128-SHA256", "ECDHE-RSA-AES256-GCM-SHA384", "ECDHE-RSA-AES256-SHA", "ECDHE-RSA-AES256-SHA384"]}'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 </TabItem> </Tabs>
 
 ### Reset to default values
@@ -129,6 +157,13 @@ curl --request PATCH \
 --data '{"value": []}'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 </TabItem> <TabItem label="per-hostname">
 
 For specific hostname settings, use the [Delete TLS setting for hostname](/api/resources/hostnames/subresources/settings/subresources/tls/methods/delete/) endpoint.
@@ -141,6 +176,13 @@ curl --request DELETE \
 --header 'Content-Type: application/json' \
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 </TabItem> </Tabs>
 
 <Render file="cipher-suites-saas-linkout" />

src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 13
 ---
 
-import { FeatureTable, TabItem, Tabs } from "~/components";
+import { FeatureTable, TabItem, Tabs, APIRequest } from "~/components";
 
 Minimum TLS Version only allows HTTPS connections from visitors that support the selected TLS protocol version or newer.
 
@@ -65,6 +65,12 @@ curl --request PATCH \
   }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 </TabItem> </Tabs>
 
 ### Per-hostname
@@ -90,6 +96,12 @@ curl --request PUT \
   }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 ## Test supported TLS versions
 
 To test supported TLS versions, attempt a request to your website or application while specifying a TLS version.

src/content/docs/ssl/edge-certificates/custom-certificates/uploading.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { Details, GlossaryTooltip, Render, TabItem, Tabs } from "~/components";
+import { Details, GlossaryTooltip, Render, TabItem, Tabs, APIRequest } from "~/components";
 
 This page lists Cloudflare requirements for custom certificates and explains how to upload and update these certificates using Cloudflare dashboard or API.
 
@@ -149,6 +149,12 @@ curl https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_certificates \
 --data "$request_body"
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 3. (Optional) Add a CAA record.
 
 <Render file="caa-records-definition" />

src/content/docs/ssl/edge-certificates/geokey-manager/setup.mdx

@@ -10,7 +10,7 @@ description: Learn how to set up Geo Key Manager and choose the geographical
   boundaries of where your private encryption keys are stored.
 ---
 
-import { Render, TabItem, Tabs, InlineBadge } from "~/components";
+import { Render, TabItem, Tabs, InlineBadge, APIRequest } from "~/components";
 
 ## Geo Key Manager v2 <InlineBadge preset="beta" />
 
@@ -49,6 +49,12 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_certificates"
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 ```bash title="Store private keys in the E.U., but not in France"
 curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_certificates" \
 --header "X-Auth-Email: <EMAIL>" \
@@ -62,6 +68,12 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_certificates"
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 :::note
 
 For more information on the `policy` field, refer to [Supported options](/ssl/edge-certificates/geokey-manager/supported-options/).

src/content/docs/ssl/origin-configuration/authenticated-origin-pull/aws-alb-integration.mdx

@@ -9,7 +9,7 @@ description: Learn how to set up Cloudflare Authenticated Origin Pulls with the
 
 ---
 
-import { Render } from "~/components";
+import { Render, APIRequest } from "~/components";
 
 This guide will walk you through how to set up [per-hostname](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/) authenticated origin pulls to securely connect to an AWS Application Load Balancer using [mutual TLS verify](https://docs.aws.amazon.com/elasticloadbalancing/latest/application/mutual-authentication.html).
 
@@ -88,6 +88,13 @@ curl --silent --request PUT \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 3. [Enable the Authenticated Origin Pulls](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/#3-enable-authenticated-origin-pulls-globally) feature on your zone.
 
 ```bash
@@ -101,6 +108,13 @@ curl --request PATCH \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 :::note
 
 Make sure your [encryption mode](/ssl/origin-configuration/ssl-modes/) is set to **Full** or higher. If you only want to adjust this setting for a specific hostname, use [Configuration Rules](/rules/configuration-rules/settings/#ssl).
@@ -129,6 +143,13 @@ curl -s --request PUT \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 2. (Optional) Use a [`GET` request](/api/resources/origin_tls_client_auth/subresources/hostnames/subresources/certificates/methods/list/) to obtain a list of the client certificate IDs. You will need the ID of the certificate you want to remove for the following step.
 
 ```bash
@@ -137,6 +158,13 @@ curl "https://api.cloudflare.com/client/v4/zones/$ZONEID/origin_tls_client_auth/
 --header "X-Auth-Key: $MYAUTHKEY"
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 3. Use the [Delete hostname client certificate](/api/resources/origin_tls_client_auth/subresources/hostnames/subresources/certificates/methods/delete/) endpoint to remove the certificate you had uploaded.
 
 ```bash
@@ -145,3 +173,10 @@ curl --request DELETE \
 --header "X-Auth-Email: $MYAUTHEMAIL" \
 --header "X-Auth-Key: $MYAUTHKEY"
 ```
+
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+

src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx

@@ -9,7 +9,7 @@ description: Encryption modes allow you to control how Cloudflare connects to
   validated.
 ---
 
-import { DirectoryListing, Render, TabItem, Tabs } from "~/components";
+import { DirectoryListing, Render, TabItem, Tabs, APIRequest } from "~/components";
 
 <Render file="encryption-mode-definition" /> <br />
 
@@ -60,6 +60,14 @@ If you want to opt a zone out via the API, you can make this API call on or befo
   --data '{"value":"custom"}'
 ```
 
+
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 #### Opt out multiple zones
 
 If you wanted to opt out multiple zones:
@@ -76,6 +84,14 @@ If you wanted to opt out multiple zones:
    --header 'Content-Type: application/json'
    ```
 
+
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 3. Create a list of zone IDs you want to opt-out with each zone ID on a separate line (newline separate), stored in a file such as `zones.txt`.
 4. Create a bash script for `opt-out-multiple-zones.sh` and add the following. Add `zones.txt` to the same directory or update the path accordingly.
 
@@ -93,6 +109,14 @@ If you wanted to opt out multiple zones:
    done
    ```
 
+
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 5. Open your command line and run:
 
    ```bash

src/content/docs/ssl/post-quantum-cryptography/pqc-to-origin.mdx

@@ -8,7 +8,7 @@ head: []
 description: Learn about post-quantum cryptography in connections from Cloudflare to your origin servers.
 ---
 
-import { Example } from "~/components";
+import { Example, APIRequest } from "~/components";
 
 As explained in [About PQC](/ssl/post-quantum-cryptography/), Cloudflare has deployed support for hybrid key agreements, which includes both the most common key agreement for TLS 1.3, X25519, and the post-quantum secure ML-KEM.
 
@@ -46,6 +46,12 @@ curl --request PUT \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 The possible values are:
 - `supported` (most compatible): Advertise support for post-quantum key agreement, but send a classical keyshare in the first ClientHello.
 - `preferred` (most performant): Send a post-quantum keyshare in the first ClientHello. Cloudflare continues to advertise support for classical keyshares as well.

src/content/partials/ssl/forward-client-certificate.mdx

@@ -3,6 +3,8 @@
 
 ---
 
+import { APIRequest } from "~/components";
+
 ## Forward a client certificate
 
 In addition to enforcing mTLS authentication for your host, you can also forward a client certificate to your origin server as an HTTP header. This setup is often helpful for server logging.
@@ -34,6 +36,13 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/access/certificates/setting
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
+
 Once `client_certificate_forwarding` is set to `true`, the first request of an mTLS connection will now include the following headers:
 
 * `Cf-Client-Cert-Der-Base64`