Sharing Data from an Existing Looker Instance
1 min
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 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 go to the admin panel (gear icon in the left nav) under users, find your account and click edit scroll down to the api3 keys section click new api3 key looker will generate a client id and client secret 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