You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/browser-rendering/rest-api/index.mdx
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,3 +25,18 @@ Before you begin, make sure you [create a custom API Token](/fundamentals/api/ge
25
25
Currently, the Cloudflare dashboard displays usage metrics exclusively for the [Workers Binding API method](/browser-rendering/workers-binding-api/). Usage data for the REST API is not yet available in the dashboard. We are actively working on adding REST API usage metrics to the dashboard.
26
26
27
27
:::
28
+
29
+
## Automatic request headers
30
+
31
+
When using the REST API to fetch content via Browser Rendering, Cloudflare adds the following headers to outbound requests made to the target URL:
|`cf-biso-request-id`| A unique identifier for the browser rendering request |
36
+
|`cf-biso-devtools`| A flag indicating the request originated from Cloudflare's rendering infrastructure |
37
+
38
+
:::note[Note]
39
+
40
+
These headers are unique to Browser Rendering and are automatically included and cannot be removed or overridden (such as via `setExtraHTTPHeaders`). They are intended to ensure transparency, allowing destination servers to identify traffic as coming from Cloudflare Browser Rendering.
0 commit comments