Looker | Operate As Docs

Connect your client's Looker with a key they paste, and call its API through Operate As.

Website: cloud.google.com/looker
Connects by: Pasting a Client ID
Category: Analytics and SEO
Services: 1
Tools: 487

Service	Key	Base URL
Looker	`looker`	`https://{instance}/api/4.0`

Your client also types their looker address (Such as yourcompany.cloud.looker.com).

Connecting

Your client makes a Client ID in their Looker settings and pastes it on their link. Operate As tries it with Looker before saving it, and stores it encrypted. See Services connected with an API key.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "looker"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "looker"    ]  }]

Permissions

What the client reads	Permission it asks for
Use the Looker key you paste, with only the access you gave that key	Chosen on the provider's screen

Tools

Install Looker's typed package for your language:

pip install operate-as-looker

pip install operate-as-looker

Run looker.accept_integration_hub_legal_agreement

curl -X POST https://api.operate.as/v1/actions/looker.accept_integration_hub_legal_agreement \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "integration_hub_id": "<integration_hub_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/looker.accept_integration_hub_legal_agreement \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "integration_hub_id": "<integration_hub_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/looker.accept_integration_hub_legal_agreement

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://{instance}/api/4.0, with the parts in braces filled in from your client's account. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../looker/user" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../looker/user" \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

A key works until your client deletes it in Looker. They can paste a new one on the same link at any time, and your workflows carry on without changes.

See Keeping access alive and Removing access.

Calls answer, once the key is deleted

{
  "status": 401,
  "data": {
    "…": "the service's own error"
  },
  "encoding": "json"
}

{  "status": 401,  "data": {    "…": "the service's own error"  },  "encoding": "json"}