Fill in APIRequest throughout

Author: RebeccaTamachiro

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

@@ -52,12 +52,22 @@ curl --request PATCH \
 ```
 
 <APIRequest
-  path=""
-  method=""
-  json={{}}
+  path="/zones/{zone_id}/custom_hostnames/{hostname_id}"
+  method="PATCH"
+  json={{
+		"ssl": {
+    "method": "http",
+    "type": "dv"
+  },
+  "custom_metadata": {
+    "customer_id": "12345",
+    "redirect_to_https": true,
+    "security_tag": "low"
+  },
+	}}
 />
 
-Changes to metadata will propagate across Cloudflare’s edge within 30 seconds.
+Changes to metadata will propagate across Cloudflare's edge within 30 seconds.
 
 ---
 
@@ -109,7 +119,7 @@ lookup_json_string(cf.hostname.metadata, "security_tag") eq "low"
 - Define fallback behaviour in the non-presence of metadata
 - Define fallback behaviour if a key or value in the metadata are unknown
 
-General guidance is to follow [Google’s JSON Style guide](https://google.github.io/styleguide/jsoncstyleguide.xml) where appropriate.
+General guidance is to follow [Google's JSON Style guide](https://google.github.io/styleguide/jsoncstyleguide.xml) where appropriate.
 
 ---
 
@@ -118,7 +128,7 @@ General guidance is to follow [Google’s JSON Style guide](https://google.githu
 There are some limitations to the metadata that can be provided to Cloudflare:
 
 - It must be valid JSON.
-- Any origin resolution — for example, directing requests for a given hostname to a specific backend — must be provided as a hostname that exists within Cloudflare’s DNS (even for non-authoritative setups). Providing an IP address directly will cause requests to error.
+- Any origin resolution — for example, directing requests for a given hostname to a specific backend — must be provided as a hostname that exists within Cloudflare's DNS (even for non-authoritative setups). Providing an IP address directly will cause requests to error.
 - The total payload must not exceed 4 KB.
 - It requires a Cloudflare Worker that knows how to process the schema and trigger logic based on the contents.
 - Custom metadata cannot be set on custom hostnames that contain wildcards.

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

@@ -49,9 +49,23 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
 ```
 
 <APIRequest
-  path=""
-  method=""
-  json={{}}
+  path="/zones/{zone_id}/custom_hostnames"
+  method="POST"
+  json={{
+		"hostname": "{hostname}",
+		"ssl": {
+			"method": "http",
+			"type": "dv",
+			"settings": {
+				"http2": "on",
+				"min_tls_version": "1.2",
+				"tls_1_3": "on",
+				"early_hints": "on"
+				},
+				"bundle_method": "ubiquitous",
+				"wildcard": false
+			},
+	}}
 />
 
 4. For an existing custom hostname, locate the `id` of that hostname via a `GET` call:
@@ -63,9 +77,11 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames?host
 ```
 
 <APIRequest
-  path=""
-  method=""
-  json={{}}
+  path="/zones/{zone_id}/custom_hostnames"
+  method="GET"
+  parameters={{
+		hostname:{hostname}
+	}}
 />
 
 5. Then make an API call such as the example below, specifying `"early_hints": "on"`:
@@ -91,9 +107,20 @@ curl --request PATCH \
 ```
 
 <APIRequest
-  path=""
-  method=""
-  json={{}}
+  path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
+  method="PATCH"
+  json={{
+		"ssl": {
+			"method": "http",
+			"type": "dv",
+			"settings": {
+				"http2": "on", // Note: These settings will be set to default if not included when updating early hints
+				"min_tls_version": "1.2",
+				"tls_1_3": "on",
+				"early_hints": "on"
+				}
+			},
+	}}
 />
 
 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/waf-for-saas/index.mdx

@@ -29,9 +29,14 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
 ```
 
 <APIRequest
-  path=""
-  method=""
-  json={{}}
+  path="/zones/{zone_id}/custom_hostnames"
+  method="POST"
+  json={{
+		"hostname": "<CUSTOM_HOSTNAME>",
+		"ssl": {
+			wildcard: false
+		},
+	}}
 />
 
 ## 1. Associate custom metadata to a custom hostname
@@ -51,9 +56,8 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
 ```
 
 <APIRequest
-  path=""
-  method=""
-  json={{}}
+  path="/zones/{zone_id}/custom_hostnames"
+  method="GET"
 />
 
 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).
@@ -81,9 +85,14 @@ curl --request PATCH \
 ```
 
 <APIRequest
-  path=""
-  method=""
-  json={{}}
+  path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
+  method="PATCH"
+  json={{
+		"custom_metadata": {
+    "customer_id": "12345",
+    "security_level": "low"
+		},
+	}}
 />
 
 This assigns custom metadata to your custom hostname so that it has a security tag associated with its ID.
@@ -119,9 +128,28 @@ curl --request PUT \
 ```
 
 <APIRequest
-  path=""
-  method=""
-  json={{}}
+  path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
+  method="PUT"
+  json={{
+		"rules": [
+			{
+				"action": "block",
+				"ratelimit": {
+					"characteristics": [
+						"cf.colo.id",
+						"ip.src"
+					],
+					"period": 10,
+					"requests_per_period": 2,
+					"mitigation_timeout": 60
+				},
+				"expression": "lookup_json_string(cf.hostname.metadata, \"security_level\") eq \"low\" and http.request.uri contains \"login\""
+			}
+		]
+	}}
+	parameter={{
+		ruleset_phase: "http_ratelimit"
+	}}
 />
 
 To build rules through the dashboard: