# Where can I find API ids?

When interacting with the GitBook API, you'll frequently need to provide specific identifiers. The most common of these are the Organization ID, Space ID, and Site ID. Fortunately, locating these IDs is straightforward – they are embedded directly within the GitBook app's URL as you navigate through your content.

**Locating Your Organization and Space IDs:**

When you're actively working within a specific space in the GitBook application, take a look at the URL displayed in your browser's address bar. It will typically resemble the following structure:

```
https://app.gitbook.com/o/<your_organization_id>/s/<your_space_id>
```

In a URL like `https://app.gitbook.com/o/50mEth1Ng/s/RaNd0Mstr1NG`, the segment following `/o/`, which is `50mEth1Ng` in this case, represents your **Organization ID**. Similarly, the portion after `/s/`, here `RaNd0Mstr1NG`, is your **Space ID**.

**Identifying Your Site ID:**

To find your Site ID, go to the dashboard for the specific site you are interested in within the GitBook app. Once on the dashboard, examine the URL in your browser. You should find a section that looks like `/sites/<your_site_id>`.

For example, if the URL contains `/sites/site_w0r1d`, then `site_w0r1d` is your **Site ID**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook-open-v2-preview.gitbook.workers.dev/url/gitbook.com/docs/help-center/where-can-i-find-api-ids.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
