Skip to main content

Looker

This connector captures data from Looker into Estuary collections.

Supported data resources​

The following data resources are supported through the Looker API:

By default, each resource is mapped to an Estuary collection through a separate binding.

Prerequisites​

  • A Looker account.
  • A Looker API key, consisting of a client ID and a client secret. See Looker's documentation for instructions on generating these credentials.

Configuration​

You configure connectors either in the Estuary web app, or by directly editing the catalog specification files. See connectors to learn more about using connectors. The values and specification sample below provide configuration details specific to the Looker source connector.

Properties​

Endpoint​

PropertyTitleDescriptionTypeRequired/Default
/credentials/client_idClient IDLooker client ID.stringRequired
/credentials/client_secretClient SecretLooker client secret.stringRequired
/credentials/credentials_titleAuthentication MethodSet to OAuth Credentials.stringRequired
/subdomainSubdomainThe subdomain for your Looker account. For example in https://estuarydemo.cloud.looker.com/folders/home, estuarydemo.cloud.looker.com is the subdomain.stringRequired

Bindings​

PropertyTitleDescriptionTypeRequired/Default
/nameData resourceName of the data resource.stringRequired
/intervalIntervalInterval between data syncsstring

Sample​

captures:
${PREFIX}/${CAPTURE_NAME}:
endpoint:
connector:
image: ghcr.io/estuary/source-looker:v1
config:
credentials:
client_id: <secret>
client_secret: <secret>
subdomain: mylookersubdomain.cloud.looker.com
bindings:
- resource:
name: dashboards
target: ${PREFIX}/dashboards