# Sitevision API
## Start with enabling the Sitevision REST API
Ebbot utilizes the Sitevision REST API to fetch Sitevision content and convert it to documents in EbbotGPT Knowledge. In order to fetch information, the REST API must be enabled within Sitevision. This can be done in Sitevision's edit mode:
1. Click the cog wheel icon in the top bar and select site settings
2. Under 'Integration' - select REST-API
3. Check 'Enable REST-API', adjust any restrictions to the API you would like to apply and click OK.
This enables the API, for more information about additional configuration, please consult the Sitevision help & documentation:
## Connecting your Sitevision instance to EbbotGPT
There are multiple settings in EbbotGPT Knowledge for the Sitevision connection, to control which content you would like the scraper to fetch. Here is a closer look at each setting:
### Domain - Required
This is the domain of your site. Enter only the domain without protocol.
**Example:** mysite.domain.com
The scraper uses the HTTPS protocol when doing API calls, adding https\:// or http\:// before the domain will not work.
### Username / Password - Optional
If your REST API is not publicly accessible, you would enter the username / password to a user that has access to the API.
\
This is marked as optional since this varies between sites, but if the API is not set to public, these credentials are required.
### Root node id - Optional
This is where the scrape will start. By default it uses the root node of your site, which means this can be left blank if you want to include the full site.
If you would like to start the scraping process at a different part of your site, you can enter the node ID of the page from where it should start.
The scraping process traverses down the site tree from the root node
### Only include pages visible in menus
Checking this box will exclude any pages that have been hidden from the navigation menu in Sitevision.
### Pages to exclude
Add the page ID's of any pages you want to exclude. If you want to exclude the specific page but include its subpages, deselect the 'Exclude subpages' checkbox.
## How to get the ID of a Sitevision page
There are two primary ways to get the ID of a page.
1. From the address bar in the Sitevision editor.\
When in Sitevision edit mode, the ID is the final part of the URL: \_\*\*
2. From the browsers console: \
By opening the page and running \`window\.sv.PageContext.pageId\` in the developer console, it will output the ID of the current page.
## Why you would want to change the Root node id
In some cases you might not want to start at the root and only grab certain parts of the site.
For example:\
\
Let’s say that we only want the EbbotGPT have knowledge about “Miljökämpen”, we would enter that page’s id.
## What nodes from Sitevision gets scraped?
The scraper get’s the following nodes:
* Text
* Block
* Inline
When getting either the block or inline nodes, it gets the HTML name and turns it into the corresponding markdown tag. If there is no corresponding tag, the node gets ignored.
---
# 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://docs.ebbot.ai/ebbot-docs/core-capabilities/ebbotgpt/ebbotgpt-knowledge/source-types/api-sources/sitevision-api.md?ask=
```
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.
