GET /api/v1/browsers — List Browser Sessions

Returns connected browser sessions. Browsers are read-only via the API. Use app-state IDs as executor_ids, not browser IDs directly.

The Browsers API returns the browser sessions connected to your ReachOwl account. Browsers are read-only resources: you cannot connect, configure, or disconnect them via the API. When creating campaigns, post schedulers, or profile growth tasks, use app-state IDs as executor_ids, not browser IDs directly.

List Browser Sessions

Endpoint

GET /api/v1/browsers

Request Example

curl -X GET 'https://reachowl.com/api/v1/browsers' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Accept: application/json'

Response Example

{
  "data": [
    {
      "id": 1,
      "name": "Chrome Session 1",
      "status": "connected",
      "created_at": "2024-01-15T10:00:00Z"
    }
  ]
}

---

Get a Browser Session

Endpoint

GET /api/v1/browsers/{id}

Path Parameters

id · integer · required

The unique identifier of the browser session.

Request Example

curl -X GET 'https://reachowl.com/api/v1/browsers/1' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -H 'Accept: application/json'

Response Example

{
  "id": 1,
  "name": "Chrome Session 1",
  "status": "connected",
  "created_at": "2024-01-15T10:00:00Z"
}

Do not use browser IDs as executor_id when creating campaigns. Use app-state IDs instead. See the App States endpoint for details.

Error Responses

Status	Description
401	Unauthorized
404	Browser session not found