---
title: "Delete location"
method: DELETE
path: "/v1/org-nodes/{id}"
tags: ["org-nodes"]
---

# Delete location

`DELETE /v1/org-nodes/{id}`

## Request

- Base URL: `https://api.brixsignage.com`
- URL: `https://api.brixsignage.com/v1/org-nodes/{id}`
- Auth: HTTP bearer

Soft-deletes a location. Everything at that location, including screens, content, folders and the people assigned there, moves to its parent location first, so nothing is left orphaned. Each person keeps their role, now at the parent location; if they already have that access there, the duplicate is dropped. Because a role at the parent applies to everything under it, you can only delete a location when you could give each of those roles at the parent yourself, and only an account owner can move an owner. People never move into another workspace: deleting a franchise workspace's top location removes the role assignments there. The root location and any location with active child locations cannot be deleted, and a deleted location cannot be restored.

**Notes.**
- Screens, content and people move to the parent location. Each person keeps their role, now at the parent, so it applies to everything under the parent. If they already have that access at the parent or above, the moved role assignment is dropped; otherwise they keep both.
- Because the move widens where a role applies, you need to be able to give each moved role at the parent yourself. That includes your own role.
- People never move into another workspace. Deleting a franchise workspace's top location removes the role assignments there.
- A deleted location cannot be restored. The activity log records where each person was moved from.

## Path parameters

- `id` string, required

## Response `200`

Success.

- object
  - `data` object, required
    - `id` string, required
    - `deleted` true, required
    - `transferredTo` string, required: The parent location that received this location's screens, content and people.
    - `membersMoved` integer, required: Role assignments moved up to the parent, including ones merged into an assignment the person already had there. 0 when the location is a franchise workspace's own top location.

## Other responses

- `401`: Missing, expired or revoked bearer token.
- `403`: You do not hold `org-unit.delete` there; `owner_required`: an owner placed here would move up and you are not an owner at the parent (an API key never is); or `outranked`: a person placed here holds a permission you do not hold at the parent.
- `404`: No such location in this workspace.
- `409`: `protected` (the workspace root), `has_children` (move or delete the child locations first), or `last_owner` (deleting a franchise workspace's top location would remove the last owner).
- `502`: A franchise workspace's own subscription could not be ended; nothing was deleted.
- `5XX`: Server error. The body carries a `requestId` to quote to support.

---

[API](https://skmtc.dev/brixsignage/apis/brix-api.md) · [All operations](https://skmtc.dev/brixsignage/apis/brix-api/llms.txt) · [OpenAPI document](https://skmtc.dev/brixsignage/apis/brix-api/revisions/7c2741bcdb16?raw)