History Back
Browser Sessions
History Back
Navigate back in the active tab’s history.
POST
History Back
Overview
The/browser/sessions/{id}/back endpoint moves the active tab one step backwards in its history stack, equivalent to clicking the browser’s back 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 previous history entry the endpoint returns 409 Conflict.
Path Parameters
string
required
Browser session ID (UUID). Create via
POST /browser/sessions.Body
All body fields are optional — the request body may be omitted entirely.string
default:"load"
When to consider the navigation finished. One of
load, domcontentloaded, networkidle.integer
default:"30000"
Maximum time (ms) to wait for navigation. Range
0–120000.Example Request
Response
Success Response (200)
string
Effective URL of the active tab after moving backwards.
string
CDP target identifier of the tab the operation applied to.
Error Responses
Notes
- Returns almost immediately when the browser’s back-forward cache (
bfcache) is warm. - A
409 Conflictmeans there is nothing to go back to — check history length before calling, or handle the error as a no-op.