Get Run Status

Minimal status poll (see RunStatusResponse). POLL rate bucket: selects ONLY the status/project columns — a 2s poll never drags the task/result text (TOAST reads) that GET /runs/ pays. Poll until terminal, then fetch the full summary once.

GET /runs/{run_id}/status

Get Run Status

JavaScript

const options = {method: 'GET', headers: {'X-Browser-Use-API-Key': '<api-key>'}};

fetch('https://api.browser-use.com/api/v4/runs/{run_id}/status', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

curl --request GET \
  --url https://api.browser-use.com/api/v4/runs/{run_id}/status \
  --header 'X-Browser-Use-API-Key: <api-key>'

import requests

url = "https://api.browser-use.com/api/v4/runs/{run_id}/status"

headers = {"X-Browser-Use-API-Key": "<api-key>"}

response = requests.get(url, headers=headers)

print(response.text)

200

{}

{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}

Authorizations

X-Browser-Use-API-Key · string · header · required

Path Parameters

run_id · string<uuid> · required

Response

200

application/json

Successful Response

Minimal poll target: just the run's status. Poll this until terminal (cheap indexed lookup, tiny payload — never the task/result text), then fetch the full RunSummary once via GET /runs/{id}. Mirrors v2's GET /tasks/{id}/status.

status · enum<string> · required

Available options: queued, dispatching, running, completed, failed, cancelled