---
title: "Get User"
method: GET
path: "/me/"
tags: ["User API"]
---

# Get User

`GET /me/`

Gets the current user

## Response `200`

Successfully retrieved current user

- OrganisationScopedUser — The authenticated user, resolved against their active organisation. ``id`` is deliberately the ACTIVE ORGANISATION id, not the user id, because every scoped table stores the organisation id in its ``user_id`` column. For a personal organisation the two are identical, which is why no existing row had to be migrated. Anything that concerns the human being rather than the workspace (the ``users`` row, VIP codes, billing) must use ``account_id``.
  - `id` string, required
  - `auth_id` string, required
  - `email` string, required
  - `read_only` boolean
  - `language` string, nullable
  - `organisation_limit` integer
  - `created_at` string, date-time, nullable
  - `is_organisation_member` boolean
  - `tier` 'sandbox' | 'pro' | 'business' | 'enterprise'
  - `account_id` string, required
  - `organisation_role` 'admin' | 'user'
  - `is_personal_organisation` boolean
  - `billing_user_id` string, required
  - `can_use_organisations` boolean, required — Whether the organisation switcher should be shown to this user. True either because they may create organisations of their own, or because they have been invited into someone else's — with a limit of 0 and no memberships the personal organisation is all they will ever have, so there is nothing to switch between.

---

[API](https://skmtc.net/toolhouse/apis/toolhouse-api.md) · [All operations](https://skmtc.net/toolhouse/apis/toolhouse-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/toolhouse/toolhouse-api/versions/6e3bad3564b3/schema)