---
title: "Browser Seat"
method: POST
path: "/v1/teams/{team_id}/teammate/browser-seat"
tags: ["teammate"]
---

# Browser Seat

`POST /v1/teams/{team_id}/teammate/browser-seat`

## Request

- Base URL: `https://api.stormy.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api.stormy.ai/v1/teams/{team_id}/teammate/browser-seat`
- Auth: none declared

He signed in to a site on screen (Connections → Sign in on screen): keep it as a seat.

Owner, 2026-10-13: "how do i connect more stuff … add more with EMAIL and SCREEN web
browser". The provider's own word decides it — a site with no signed-in seat in the team's
browser profile is refused — and the record is the same `connections/<host>.md` a desk's
sign-in writes, so the Connections list and the desk both see it.

## Path parameters

- `team_id` string, uuid, required

## Headers

- `authorization` string, nullable
- `x-darwin-token` string, nullable

## Request body

- SeatAsk
  - `domain` string, required

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

## Changes

> 68 revisions in range; 1 not diffed.

- **2026-10-14** `f65dcc3528d4`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/stormy/apis/stormy-control-plane/changes/v1/teams/:team_id/teammate/browser-seat/post.md)

---

[API](https://skmtc.dev/stormy/apis/stormy-control-plane.md) · [All operations](https://skmtc.dev/stormy/apis/stormy-control-plane/llms.txt) · [OpenAPI document](https://skmtc.dev/stormy/apis/stormy-control-plane/revisions/a40e83844eaa?raw)