Add placeholder component syntax

Author: RebeccaTamachiro

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata.mdx

@@ -51,6 +51,12 @@ curl --request PATCH \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 Changes to metadata will propagate across Cloudflare’s edge within 30 seconds.
 
 ---

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx

@@ -48,6 +48,12 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 4. For an existing custom hostname, locate the `id` of that hostname via a `GET` call:
 
 ```bash
@@ -56,6 +62,12 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames?host
 --header "X-Auth-Key: <API_KEY>"
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 5. Then make an API call such as the example below, specifying `"early_hints": "on"`:
 
 ```bash
@@ -78,4 +90,10 @@ curl --request PATCH \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 Currently, all options within `settings` are required in order to prevent those options from being set to default. You can pull the current settings state prior to updating Early Hints by leveraging the output that returns the `id` for the hostname.

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/custom-certificates/certificate-signing-requests.mdx

@@ -82,6 +82,12 @@ curl https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_csrs \
 }
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 Replace the `\n` characters with actual newlines before passing to your customer. This can be accomplished by piping the output of the prior call to a tool like jq and perl, such as:
 
 ```bash
@@ -92,6 +98,12 @@ curl https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_csrs \
 --data "$request_body" | jq .result.csr | perl -npe s'/\\n/\n/g; s/"//g' > csr.txt
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 ### 3. Customer obtains certificate
 
 Your customer will take the provided CSR and work with their CA to obtain a signed, publicly trusted certificate.
@@ -133,4 +145,10 @@ You can request the (paginated) collection of all previously generated custom CS
 
 Delete one or more of the CSRs to delete the underlying private key by making a `DELETE` request to `https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_csrs/{csr_id}`.
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 You may delete a CSR provided there are no custom certificates using the private key that was generated for the CSR. If you attempt to delete a CSR whose private key is still in use, you will receive an error.

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx

@@ -28,6 +28,12 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
 --data '{"Hostname":"example.com"}, "Ssl":{wildcard:false}}'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 ## 1. Associate custom metadata to a custom hostname
 
 To apply WAF to your custom hostname, you need to create an association between your customer's domain and the WAF configuration that you would like to attach to it. Cloudflare's product, [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/) allows you to do this via the API.
@@ -44,6 +50,12 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
 --header "X-Auth-Key: <API_KEY>"
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 4. Plan your [custom metadata](/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata/). It is fully customizable. In the example below, we have chosen the tag `"security_level"` to which we expect to assign three values (low, medium, and high).
 
 :::note
@@ -68,6 +80,12 @@ curl --request PATCH \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 This assigns custom metadata to your custom hostname so that it has a security tag associated with its ID.
 
 ## 2. Trigger security products based on tags
@@ -100,6 +118,12 @@ curl --request PUT \
 }'
 ```
 
+<APIRequest
+  path=""
+  method=""
+  json={{}}
+/>
+
 To build rules through the dashboard:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and navigate to your account and website.