Skip to content

Commit bd43b3f

Browse files
request headers
1 parent d3853dc commit bd43b3f

File tree

1 file changed

+15
-0
lines changed
  • src/content/docs/browser-rendering/rest-api

1 file changed

+15
-0
lines changed

src/content/docs/browser-rendering/rest-api/index.mdx

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,18 @@ Before you begin, make sure you [create a custom API Token](/fundamentals/api/ge
2525
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.
2626

2727
:::
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:
32+
33+
| Header | Description |
34+
| -------------------- | ----------------------------------------------------------------------------------- |
35+
| `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.
41+
42+
:::

0 commit comments

Comments
 (0)