> 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/data-pipeline-tools/stitch.md).

# Stitch

An overview of the Stitch integration with Secoda

{% content-ref url="/pages/mmYSwfTnwipXGoP4oGwG" %}
[Stitch Metadata Extracted](/integrations/data-pipeline-tools/stitch/stitch-metadata-extracted.md)
{% endcontent-ref %}

## Getting Started with Stitch <a href="#h_21e27f5a15" id="h_21e27f5a15"></a>

There are two steps to get started using Stitch with Secoda:

1. Retrieve your Stitch Client ID
2. Generate an API Key on Stitch
3. Connect Stitch to Secoda with your API Key and API Secret

{% hint style="info" %}
Secoda pulls the following metadata from the Stitch API: jobs, run times, owners, destinations, and other general metadata around jobs.
{% endhint %}

### Retrieve your Stitch Client ID

Your Stitch client ID can be found in the URL of your Stitch instance. For example, the client ID for`https://app.stitchdata.com/client/210396/pipeline/v2/welcome` is 210396.

### Generate an API Key

1. Login to Stitch and head to the Settings > Account Settings section.
2. Generate an API Access Key

### Connect Stitch to Secoda

1. In Secoda, head to the **Integrations** page and click **New Integration**
2. Select **Stitch**
3. Paste the API Key
4. Head to the **Sync History** tab on the side bar and click **Run sync**


---

# 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/data-pipeline-tools/stitch.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.