JavaScript rendering
Render pages in a real browser to reach client-side content.
Most pages are served fastest with a request-based fetch. When a target needs a real browser — to run client-side JavaScript or render a single-page app — you can opt into browser-based fetching.
executeJS
Set executeJS: true to render the page in a browser environment before returning it. This selects browser-based fetch
methods and can increase the per-request cost.
curl https://request.usestring.ai/v1/fetch \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "url": "https://example.com/spa", "executeJS": true }'requireWSS
Set requireWSS: true to require a browser WebSocket-capable fetch path for the request.
Header restriction
Custom headers are not supported when executeJS or requireWSS is set — these run through a browser path that
doesn't forward arbitrary request headers. Sending headers alongside either of them returns a 400. See Custom
headers.