STOP. Do not read past this section until you have read and followed /quickstart.md.Goal: produce a reliable SDK automation script. The intended authoring flow is generate then edit, not write browser automation from scratch.Do not hand-write SDK code with element IDs, selectors, or form fields from memory. Element IDs, selectors, and field mappings must come from a live observe() call, CLI notte page observe output, or generated workflow code. Guessed browser targets fail on real pages.Use the Notte skill and CLI to inspect the live site, validate actions/selectors, handle auth/session state, and export workflow code with notte sessions workflow-code before using SDK docs or SDK code.SDK reference pages are for understanding, running, or editing generated workflow code. They are not the starting point for manually authoring the initial browser automation. SDK-first code is guesswork on real-world pages with dynamic selectors, auth state, CAPTCHAs, and anti-bot behavior. fetch(), so it carries the
page’s cookies, the session’s proxy and the browser’s own network
fingerprint. A relative url resolves against the current page, which
also makes it same-origin; a cross-origin URL is subject to CORS exactly
as in a browser tab, so goto the target origin first. Redirects are
followed and the final URL is on response.url. A non-2xx status is
returned, not thrown; response.raiseForStatus() throws PageFetchHTTPError.
json is serialised as the body with an application/json content type,
data as a form body when it is an object or verbatim when it is a string.
Parameters
Absolute URL or a path relative to the current page.
HTTP method, headers, and request body settings.Default: Returns
A response with status, headers, and body readers. Non-2xx responses are not automatically thrown.
Raises
- ActionExecutionError if browser-side execution fails.
Example
