> For the complete documentation index, see [llms.txt](https://docs.tiny.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiny.plus/api/endpoints/me.md). # Current user `GET` `https://api.tiny.plus/me` Returns the person a token belongs to: their team member record, the account the token is acting for, what that person may see, and the account's integrations. This is the first call to make with a new token — it confirms the token works and tells you who and which account you're acting as. {% hint style="info" %} `/me` sits beside `/v2`, not under it: the URL is `https://api.tiny.plus/me`. It always answers for the account the token belongs to. See [Choosing an account](/api/concepts/requests.md#choosing-an-account). {% endhint %} ```bash curl "https://api.tiny.plus/me" \ -H "Authorization: Bearer {{user_access_token}}" ``` ```json { "id": "1231", "name": "Nick Smith", "email": "nick@example.com", "role": "Director", "timezone": "Australia/Sydney", "record_url": "https://crm.tiny.plus/staff/1231", "account": { "account_id": "3", "account_name": "Cupcake Architecture", "account_status": "active", "account_logo": "account_logos/44586e5c9d0bc6c26580aaf0e62effdb.jpg", "account_timezone": "Australia/Sydney", "account_currency": "AUD" }, "permissions": { "show_fees": true, "account_admin": true, "support_page": false, "newsfeed_admin": true, "all_records": { "projects": true, "companies": true, "contacts": true } }, "integrations": { "synergy": true, "relationship_plans": true, "bid_teams": true, "ai_ask": true, "ai_ask_posts": true, "mcp": true, "ai_posts": true }, "api_features": ["linked_to", "lists", "list_key_contacts"], "appearance": "", "post_box": "ai", "post_box_ai_used": true, "extra_accounts": [] } ``` {% hint style="info" %} `id` is the token user's team member id. It's the id to send as `staff`, `assigned_user` or `created_user` elsewhere in the API, and the one their own records are created under. {% endhint %} ## The response Alongside the fields below, the response carries the person's full team member record — the same fields as a `GET /v2/staff/{id}`, such as `mobile`, `linkedin` and `timezone`. See [Team Members](/api/endpoints/team-members.md). | Field | Description | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `id` | The person's team member id. | | `name`, `email`, `role` | Their name, email address and job title. | | `timezone` | The person's own time zone. Stamps in the API are still UTC; see [Requests](/api/concepts/requests.md). | | `account` | The account the token is acting for: `account_id`, `account_name`, `account_status`, `account_logo` (a storage path, not a URL), `account_timezone` and `account_currency`: the three-letter code of the currency every amount is in, or `null` when the account has never chosen one, in which case show amounts with `$`. | | `permissions` | What this person may see. See [Permissions](/api/concepts/permissions.md). | | `integrations` | Which integrations the account has switched on (see below). | | `api_features` | Newer parts of the API that this one has: the list parameter [`linked_to`](/api/concepts/listing.md#records-linked-to-another-record), `lists` for the [Lists](/api/endpoints/lists.md) endpoints, and `list_key_contacts` for a list's own [key contacts](/api/endpoints/lists.md#key-contacts). An older API ignores a parameter it doesn't know and answers `404` for an endpoint it doesn't have, so check here before relying on one. | | `appearance` | The person's choice of light or dark for tiny+ on the web, in this account: `light`, `dark`, or `""` to follow their computer. | | `post_box` | Which post box tiny+ opens first for this person in this account, `ai` or `plain`: the one they last chose, switched to or posted from. `plain` where they have never chosen. | | `post_box_ai_used` | Whether this person has posted from the AI post box in this account. | | `extra_accounts` | The person's other accounts, when the token isn't limited to one. Empty for a token issued for a single account, which is the usual case. Each entry repeats `account`, `permissions`, `integrations`, `appearance`, `post_box` and `post_box_ai_used` for that account. | ### `permissions` | Key | Meaning | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `show_fees` | Whether this person sees fee values in tiny+. The API returns fee fields either way, so hide them in your own screens when this is `false`. | | `account_admin` | Whether this person is an admin of this account. Only an admin can set `created_user`, `modified_user`, `created_date` or `modified_date` to anything but their own. See [Permissions](/api/concepts/permissions.md#a-token-acts-as-a-person). | | `support_page` | Whether the account shows its Support Docs page in tiny+'s menu. | | `newsfeed_admin` | Whether this person is a news feed admin, who can add channels and change the followers of any record. Account admins always are. | | `all_records` | For `projects`, `companies` and `contacts`: whether this person may see the whole account's [pipeline statistics](/api/endpoints/stats.md). It doesn't change which records a list returns. | ### `integrations` Each is `true` when the account has that integration switched on. | Key | Meaning | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | `synergy` | Total Synergy sync. | | `relationship_plans` | [Relationship plans](/api/endpoints/relationship-plans.md), which come with the Pro plan. | | `bid_teams` | [Bid teams](/api/endpoints/bid-teams.md), which come with the Pro plan and which an account admin turns on under Account Settings → Projects. | | `lists` | [Lists](/api/endpoints/lists.md). `false` only on an account that has Lists hidden from its menu. | | `ai_ask` | The Ask feature, for [turning plain English into filters](/api/endpoints/ai-filter.md). | | `ai_ask_posts` | Ask over the News Feed. | | `mcp` | The [MCP server](/api/getting-access/ai-assistants.md) — `true` only when this person holds an AI Assistants seat and the account's switch is on. | | `ai_posts` | The AI post box in tiny+'s News Feed: `true` only when this person holds an AI Assistants seat and the account's AI posts switch is on. | ## Errors A missing, malformed, expired or revoked token gives `401`, in the OAuth error shape: ```json { "error": "access_denied", "error_description": "The resource owner or authorization server denied the request.", "hint": "Missing \"Bearer\" token" } ``` See [Errors](/api/concepts/requests.md#errors).