---
title: "List Organization Folders"
method: GET
path: "/api/me/organizations/{tenant_id}/domains"
tags: ["me"]
---

# List Organization Folders

`GET /api/me/organizations/{tenant_id}/domains`

## Request

- Base URL: `https://app.thinqos.com` (the document declares no server; this is the origin it was published from)
- URL: `https://app.thinqos.com/api/me/organizations/{tenant_id}/domains`
- Auth: none declared

The folders this organization keeps, as this member reaches them.

An organization has MANY root folders, not one: verified against production
2026-09-02 the ai4o tenant has 17. So the answer is a list and the page
renders it as one, rather than a single "the organization's folder".

Scoped to what the CALLER reaches, through the same
``_reachable_org_library_ids`` the help agent's retrieval uses. A member
invited to one root must not learn the names of the other sixteen by
opening the organization page: membership of a company is not membership of
every filing cabinet in it, which is the exact inversion of the proxy
TOS-4113 retired.

A separate call rather than a field on the organization detail. Every
mutation on that page returns the whole organization, so folding the folder
tree into it would re-run this query on each role change for a list that
cannot have altered.

## Path parameters

- `tenant_id` string, uuid, required

## Headers

- `x-impersonate-identity-id` string, nullable

## Response `200`

Successful Response

- OrganizationDomainOut[]
  - `id` string, uuid, required
  - `display_name` string, required
  - `address` string, nullable, required
  - `is_root` boolean, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/thinqos/apis/thinqos-api.md) · [All operations](https://skmtc.dev/thinqos/apis/thinqos-api/llms.txt) · [OpenAPI document](https://skmtc.dev/thinqos/apis/thinqos-api/revisions/5387b4ded614?raw)