History Forward
Browser Sessions
History Forward
Navigate forward in the active tab’s history.
POST
History Forward
Overview
The/browser/sessions/{id}/forward endpoint moves the active tab one step forwards in its history stack, equivalent to clicking the browser’s forward button. The call blocks until the configured wait condition is met or the timeout elapses.
When the browser’s back-forward cache is warm, this returns almost instantly. If there is no next history entry the endpoint returns 409 Conflict.
Path Parameters
Browser session ID (UUID). Create via
POST /browser/sessions.Body
All body fields are optional — the request body may be omitted entirely.When to consider the navigation finished. One of
load, domcontentloaded, networkidle.Maximum time (ms) to wait for navigation. Range
0–120000.Example Request
Response
Success Response (200)
Effective URL of the active tab after moving forwards.
CDP target identifier of the tab the operation applied to.
Error Responses
| Status | Description |
|---|---|
401 | Unauthorized — invalid or missing API key. |
404 | Session not found or not owned by the caller. |
408 | Navigation did not complete before timeout elapsed. |
409 | No next history entry — the active tab is already at the newest entry. |
503 | The browser session is temporarily unreachable. |
Notes
- Returns almost immediately when the browser’s back-forward cache (
bfcache) is warm. - A
409 Conflictmeans there is nothing to go forward to — typically this happens after a fresh navigation, which wipes the forward stack.