Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There is an example generic HTTP connector config for the Google Maps API #1259

Closed
9 tasks done
izgeri opened this issue Jun 18, 2020 · 1 comment · Fixed by #1311
Closed
9 tasks done

There is an example generic HTTP connector config for the Google Maps API #1259

izgeri opened this issue Jun 18, 2020 · 1 comment · Fixed by #1311

Comments

@izgeri
Copy link
Contributor

izgeri commented Jun 18, 2020

Use case

I am building an app that needs to query the Google Maps API

Additional details

  • There needs to be some way for Secretless to authenticate using HTTP query parameters rather than through Authorization headers

The Google Maps APIs accept an API key through its query params.

These are the potential APIs that can be supported by a connector that uses our new queryParams key/value pair to accept a Google API Key:

Routes:

  • Directions API
  • Distance Matrix API
  • Roads API

Places:

  • Places API
  • Time Zone API
  • Geocoding API
  • Geolocation API

Acceptance criteria

@mdodell
Copy link
Contributor

mdodell commented Jun 22, 2020

Many of the Google Maps APIs use an API key that is passed in via a parameter, i.e. the Directions API, rather than through Authorization headers.

Based off of discussion, it looks like the generic HTTP connector would require support for query parameters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants