> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/api/getting-the-workspace-id.md).
# Getting the workspace ID
When using the API to perform tasks, you use the workspace ID to identify the workspace.
## Copying the workspace ID to the clipboard
From the Tonic Structural application, you can copy the workspace ID to the clipboard.
On the workspace management view, from the workspace actions menu, select **Copy Workspace ID**.
On **Workspaces** view, from the workspace actions menu, select **Copy ID to Clipboard**.
## Using the API to search for a workspace
You use [**GET**** api/workspace/search**](https://app.tonic.ai/apidocs/index.html#/Workspace/Search) to search for a workspace. You can search for workspaces based on the following:
* The workspace name
* The workspace owner
* The status of the most recent job
* The type of data connector
* Your role within the workspace
* Tag values assigned to the workspace
For each workspace, the results include the workspace ID.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tonic.ai/app/api/getting-the-workspace-id.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
