> ## Documentation Index > Fetch the complete documentation index at: https://docs.tiro.ooo/llms.txt > Use this file to discover all available pages before exploring further. # Get My Workspace > **Deprecated.** Use `GET /v1/external/workspaces` and pass the chosen `guid` explicitly. This endpoint stays available for backward compatibility. Returns a workspace only when the API key can access exactly one. A key that can access two or more workspaces gets `409` with the candidates in `error.detail.workspaces`; a key that can access none gets `404`. ## OpenAPI ````yaml /openapi.yaml get /v1/external/workspaces/me openapi: 3.1.0 info: title: Tiro API description: AI-powered note-taking and voice file processing API version: 1.0.0 contact: name: Tiro Support email: support@tiro.ooo url: https://tiro.ooo servers: - url: https://api.tiro.ooo description: Production server security: - BearerAuth: [] tags: - name: Workspace description: > List the workspaces an API key can reach. Workspace-scoped endpoints take a `{workspaceGuid}` path segment; get it from `GET /v1/external/workspaces`. - name: Note description: Operations for managing notes and their paragraphs - name: Note Share Link description: Manage share links for notes - name: Note Summary description: Operations for retrieving note summaries - name: Note Document description: Template-based document generation from notes - name: Note Document Template description: Operations for managing note document templates - name: Folder description: Operations for retrieving folders - name: Voice File description: Operations for voice file processing - name: Word Memory description: > Manage word memories to improve voice transcription accuracy. Register important terms like company names, people's names, and product names so Tiro recognizes them precisely during recording. Each term has an `entry` and an optional `subEntry` (an alternate spelling or notation). Personal (User), workspace-shared (Workspace), and organization-shared (Organization) word memories are managed separately, and each scope supports bulk create/update/delete (up to 1000 items per request). - name: Wiki description: | Access workspace wikis — unified knowledge graphs built from notes. Requires a workspace with wiki plan and activation enabled. - name: Organization description: > Endpoints for organization API keys. An organization key is issued by an organization admin, carries fixed scopes chosen at issuance, and can reach the notes in every workspace that belongs to the organization. Built for server-to-server integrations such as CRM sync — receive `note.ended` webhook events, generate documents for notes, and reconcile with the organization notes list. - name: Organization Management description: Operations for the authenticated user's organization. paths: /v1/external/workspaces/me: get: tags: - Workspace summary: Get My Workspace description: > **Deprecated.** Use `GET /v1/external/workspaces` and pass the chosen `guid` explicitly. This endpoint stays available for backward compatibility. Returns a workspace only when the API key can access exactly one. A key that can access two or more workspaces gets `409` with the candidates in `error.detail.workspaces`; a key that can access none gets `404`. operationId: getMyWorkspace responses: '200': description: The caller's implicit workspace content: application/json: schema: $ref: '#/components/schemas/WorkspaceMeResponse' example: guid: ws_abc123 '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/Error' '404': description: No workspace is accessible with this API key content: application/json: schema: $ref: '#/components/schemas/Error' '409': description: > The API key can access two or more workspaces. `error.detail.workspaces` lists the candidates; pass one `guid` as `{workspaceGuid}` on the workspace-scoped endpoints. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: 409028 errorType: conflict message: >- This API key can access 2 workspaces; specify one explicitly. detail: workspaces: - guid: ws_abc123 name: Acme Corp - guid: ws_def456 name: Personal deprecated: true components: schemas: WorkspaceMeResponse: type: object required: - guid properties: guid: type: string description: The caller's implicit workspace GUID example: ws_abc123 Error: type: object required: - error properties: error: type: object required: - code - errorType - message properties: code: type: integer description: > 6-digit error code in `AAABBB` form: first 3 digits match the HTTP status, last 3 digits are a per-status serial (e.g. `404018`). Use only when you need to distinguish specific error cases within the same HTTP status — values may be added or renumbered across releases. For general client branching, prefer `errorType`. example: 404018 errorType: type: string description: > Stable, coarse-grained error category. Recommended default for client-side branching: the value-to-status mapping is part of the API contract and will not change without a breaking-change notice. Typical use: - `unauthorized` → trigger re-authentication - `forbidden` → surface a permission error to the user - `not_found` → treat as missing resource - `too_many_requests` → back off and retry - `internal_error` → retry with exponential backoff enum: - bad_request - unauthorized - forbidden - not_found - not_acceptable - conflict - payload_too_large - unprocessable_entity - too_many_requests - internal_error example: not_found message: type: string description: >- Human-readable error message. Not stable; do not use for branching. example: 'No team found for user #217' detail: description: >- Additional error details. Authorization failures may include a reason and required scopes. oneOf: - type: string nullable: true - type: object additionalProperties: true properties: reason: type: string example: insufficient_scope required: type: array items: type: string example: - folder:read example: null securitySchemes: BearerAuth: type: http scheme: bearer description: > API key in format `{id}.{secret}`. The notes an endpoint returns depend on the key type. A **user key** reaches the notes that user can see in the app, including notes in their own private folders. A **system key** (workspace or organization, no user identity) reaches only notes that sit in a folder shared with all workspace members. Notes in a private folder, in a folder shared with only some members, or in no folder at all fall outside a system key's read scope, and scopes do not widen that boundary. List and search endpoints drop out-of-scope notes from the response without an error. Single-note reads and their sub-resources return `404`, the same response as a deleted note. See [What notes a system key reads](https://docs.tiro.ooo/en/developers/fundamentals/system-key-note-scope). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.