---
title: "Workspaces"
description: "List the workspaces a token can be used for and read their keys."
---

> Documentation Index
> Fetch the complete documentation index at: https://tarkle.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces

`GET /workspaces` is the one call a token can make without naming a workspace. It lists every workspace the token's creator can reach now, with the key each other call needs.

| Method and path | Scope | What it does |
| --- | --- | --- |
| `GET /workspaces` | any | The workspaces this token can be used for |

```bash
curl -H "Authorization: Bearer $TARKLE_TOKEN" https://tarkle.com/api/v1/workspaces
```

```json
{
  "workspaces": [
    { "workspace_key": "abcd1234", "name": "Studio", "url": "https://studio.tarkle.com", "relationship": "owner" }
  ]
}
```

| Field | Meaning |
| --- | --- |
| `workspace_key` | The 8-character key to send as `X-Workspace-Key` |
| `name` | The workspace name |
| `url` | The workspace address |
| `relationship` | `owner`, `member` or `linked` |

The internal workspace id is never shown. See [Authentication](/docs/get-started/authentication) for how keys are used.

Source: https://tarkle.com/docs/api/workspaces/index.mdx