Navigate back in the active tab’s history.
/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.
POST /browser/sessions.load, domcontentloaded, networkidle.0–120000.| 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 previous history entry — the active tab is already at the oldest entry. |
503 | The browser session is temporarily unreachable. |
bfcache) is warm.409 Conflict means there is nothing to go back to — check history length before calling, or handle the error as a no-op.