Google Maps Platform | Operate As Docs

Google Maps Platform: places, geocoding, routes, address validation, weather, air quality, pollen and solar

Website: mapsplatform.google.com
Connects by: Pasting a API key
Category: Analytics and SEO
Part of: Google Cloud
Tools: 24

Service	Key	Base URL
Google Maps Platform	`google-maps`	`https://places.googleapis.com/v1`

Connecting

Your client makes a API key in their Google Cloud settings and pastes it on their link. Operate As tries it with Google Cloud 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": [
      "google-maps"
    ]
  }
]

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

Permissions

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

Tools

Install Google Maps Platform's typed package for your language:

pip install operate-as-google-maps

pip install operate-as-google-maps

Run google-maps.addressvalidation_provide_validation_feedback

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

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

Every input, with its JSON Schema: GET /v1/actions/google-maps.addressvalidation_provide_validation_feedback

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://places.googleapis.com/v1. 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-.../google-mapsPOST /places:searchText" \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../google-mapsPOST /places:searchText" \  -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 Google Cloud. 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"}