---
title: "Place View"
method: PATCH
path: "/v1/teams/{team_id}/views/{ref}"
tags: ["stations"]
---

# Place View

`PATCH /v1/teams/{team_id}/views/{ref}`

Take a screen off the rail, or put it back at a rank.

A STARTER SCREEN IS TAKEN OFF BY OVERRIDING IT, NOT BY EDITING OURS. The
rail merges `harnesses/workspace/` with the shop's tree and the shop's copy
wins by `ref` — that override is what `presented` is built on. So a shop
that wants our Morning Pulse off its rail gets its own copy of the record
with the rank cleared, committed to its own tree, and our template is
untouched for every other shop on the box.

## Path parameters

- `team_id` string, uuid, required
- `ref` string, required

## Headers

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

## Request body

- RailPlacement — Where a screen sits down the left — or nothing, which is off it.
  - `rail` integer, nullable

## Response `200`

Successful Response

- PageWrite — What the tree looks like now, and the commit that made it so.
  - `ref` string, required
  - `rail` integer, nullable
  - `commit` string
  - `removed` string[]
  - `pushed` boolean
  - `push_reason` string

## Other responses

- `422` — Validation Error

---

[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-service-production.skmtc.workers.dev/v1/apis/stormy/stormy-control-plane/revisions/032c0f4e1565/schema)