> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/integrations/query-engines/starburst.md).

# Starburst

An overview of the Starburst integration with Secoda

{% content-ref url="/pages/9Di8IzH81NIWcGNmjjnb" %}
[Starburst Metadata Extracted](/integrations/query-engines/starburst/starburst-metadata-extracted.md)
{% endcontent-ref %}

## Get Started With Starburst

There are three steps to connect Starburst with Secoda:

1. Create an API auth token
2. Retrieve your starburst instance URI
3. Connect Starburst to Secoda

#### **Create a Starburst API auth token**

The Starburst API uses authentication tokens to allow access, so create a new auth token for secoda by following these steps:

1. From your Starburst home page, navigate to the left sidebar
2. Under the ‘Access’ dropdown, click on the ‘API auth token’ header

<figure><img src="https://secoda-public-media-assets.s3.amazonaws.com/d532ceb3-7793-4664-9c86-6db5c99c05d6.png" alt=""><figcaption></figcaption></figure>

3. Click the ‘Generate new token’ button
4. Assign a role that has access to the tables you wish to extract and optionally add a description
5. Save the Client ID and Secret Key to be entered into Secoda

#### **Retrieve your Starburst instance URI**

This is the URI that your workspace hosted in and can be found in the URL whenever you are logged in and in the workspace you want to bring into Secoda. This host will be in the format of https\://{custom-instance}.galaxy.starburst.io, where the {custom-instance} is specific to your workspace.

For example, when you are on the home page of Starburst (navigated to by clicking in the top left corner on the Starburst logo), your URL will be <https://secoda.galaxy.starburst.io/home> so your host will be <https://secoda.galaxy.starburst.io> in this case.

#### **Starburst user email and password**

Starburst uses a user email and password to extract the query history and table lineage of the Starburst workspace so these extra credentials are required by Secoda to have a complete picture of Starburst.

#### **Connect Starburst to Secoda**

After creating a Starburst user, the next step is to connect Starburst to Secoda:

1. In the Secoda App, navigate to the 'Integrations' tab.
2. Click on ‘Add Integration’.
3. Search for and select ‘Starburst’.
4. Enter the details for your Starburst workspace, including the host URI, authentication token client ID and secret key
5. Add a user email and password to enable lineage and query extraction
6. Click 'Connect'.


---

# 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.secoda.co/integrations/query-engines/starburst.md?ask=<question>&goal=<user_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.
