---
title: "Get Mind Write Access"
method: GET
path: "/api/mind/v2/perspective/{identity_id}/write-access"
tags: ["mind-v2"]
---

# Get Mind Write Access

`GET /api/mind/v2/perspective/{identity_id}/write-access`

## 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/mind/v2/perspective/{identity_id}/write-access`
- Auth: none declared

Report the caller's authorship of this Mind. Read-only.

Gated by the READ check, deliberately: a member who may see the Mind may
also see whether they are allowed to change it. It reports the decision the
write gate would make; it never makes one.

## Path parameters

- `identity_id` string, uuid, required

## Headers

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

## Response `200`

Successful Response

- V2MindWriteAccessResponse: Whether the caller may author this Mind, and under what role. TOS-4077. The Mind page needs this because "am I looking at someone else's Mind" stopped being the same question as "may I edit this Mind" once an organization could own one: an org member is always viewing another identity, yet an edit or admin member is exactly the person who should see the Add-belief control. ``role`` is null for a non-org target.
  - `identity_id` string, uuid, required
  - `can_write` boolean, required
  - `role` string, nullable

## 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/5fdd1072e877?raw)