> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/analyze-with-dashboards/sharing-data-from-an-existing-looker-instance.md).

# Sharing data from an existing Looker instance

If your organization already runs Looker, Chord can connect to it directly using an API3 key. This guide walks you through generating that key and getting it to your Chord contact securely.

**What you'll need**

* Admin access to your Looker instance (or a Looker Admin who can do this step for you)
* A password manager or secrets vault to store the credentials
* About 5 minutes

**How to get your Looker API3 key**

1. Log in to your Looker instance as an Admin. If you don't have admin access, ask your Looker Admin to complete these steps on your behalf.
2. Go to the Admin panel (gear icon in the left nav).
3. Under Users, find your account and click Edit.
4. Scroll down to the API3 Keys section.
5. Click New API3 Key. Looker will generate a Client ID and Client Secret.
6. Copy both values immediately. The Client Secret is only shown once and can't be retrieved again later. If it's lost, you'll need to delete the key and generate a new one. Store both values securely in a password manager or secrets vault. This is what Chord will use for API authentication.

**Note**: API3 keys are tied to the permissions of the user they're created under. Make sure the account has the appropriate role and permissions for whatever API access is needed (for example, read access to the specific models and explores Chord will query).

**Sharing the credentials with Chord** Once you have your Client ID and Client Secret, send both values to your Chord contact through a secure channel (a shared secrets vault or an encrypted message) rather than plain email or chat.

Avoid sending the ID and Secret in the same message thread as other unrelated credentials.

Questions or feedback? Reach out to <help@chord.co>.


---

# 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.chord.co/analyze-with-dashboards/sharing-data-from-an-existing-looker-instance.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.