---
title: "work: browse open"
description: "a `BrowseOpenInput` to the session, opened, with its live view"
section: reference
address: /reference/work/browse_open
contract: 0476e35e6e275db5
---

# work: browse open

a `BrowseOpenInput` to the session, opened, with its live view

[figure: The caller sends BrowseOpenInput to /v1/work/browse_open. The platform returns a card whose body is BrowsingSession.]

<span class="op-method">POST</span><span class="op-path">/v1/work/browse_open</span><span class="op-note">a task, 202</span>

Open a browsing session. The call needs the strategy rung under a token with the work grant, and it is served by either, by the size bound.

The route takes [BrowseOpenInput](/concepts/browseopeninput) and returns a card whose body is [BrowsingSession](/concepts/browsingsession).



## Request body
The request body is [BrowseOpenInput](/concepts/browseopeninput).



| field | type | required | note |
|---|---|---|---|
| `strategy` | `id` | no |  |
| `identity` | `id` | no |  |
| `proxy_policy` | [ProxyPolicy](/concepts/proxypolicy) | no |  |
| `filter` | [ResourceFilter](/concepts/resourcefilter) | no |  |
| `live_view` | `bool` | yes |  |



## Response
The route returns a card whose body is [BrowsingSession](/concepts/browsingsession). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true. This route runs as a long step and returns a task with status 202. `POST /v1/work/status` returns the task's progress, and `POST /v1/work/cancel` stops the task.

## Headers


| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/<id>, then /brand/<id>, then /strategy/<id> |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |



A caller needs the strategy rung and a token with the work grant. The platform or the desktop app serves this route.

## Example
The example sends the smallest body that BrowseOpenInput allows. The build validates it against the schema of BrowseOpenInput.

<details class="wire"><summary>Example</summary>





```sh
curl -X POST https://api.scaleintelligence.co/v1/work/browse_open \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "live_view": false }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.work.browse_open({
    "live_view": false
  });
// answer.body is a BrowsingSession. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/work/browse_open",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "live_view": false
    }).json()
```




```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/work/browse_open")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&BrowseOpenInput { /* the fields of the page */ }).send().await?.json().await?;
```




</details>

## MCP tool
The MCP tool `si.work.browse_open` takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/BrowsingSession`. The [tool's page](/reference/tools/si-work-browse_open) describes it.