Google: Security Definitions missing (apiKey)

[rbren]

No description provided.

[IvanGoncharov]

Do you mean it require api key?

[rbren]

I'm not sure how it's supposed to handle auth, but it's a paid API so I
know it uses some kind of auth

Bobby Brennan
bobby.brennan@gmail.com

On Thu, Feb 25, 2016 at 4:33 PM, Ivan Goncharov notifications@github.com
wrote:

Do you mean it require api key?

—
Reply to this email directly or view it on GitHub
#35 (comment)
.

[IvanGoncharov]

@bobby-brennan All Google APIs have this parameter:
https://github.com/APIs-guru/api-models/blob/master/APIs/googleapis.com/translate/v2/swagger.yaml#L40

[rbren]

I'd argue that key and oauth_token should be in security definitions. For
example you have to re-enter your API key in the lucybot console each time
you change operations, but if it's a secdef the console will remember it

Having it as a parameter is sufficient though, especially if it's not an
easy fix
On Feb 25, 2016 5:37 PM, "Ivan Goncharov" notifications@github.com wrote:

@bobby-brennan https://github.com/bobby-brennan All Google APIs have
this parameter:

https://github.com/APIs-guru/api-models/blob/master/APIs/googleapis.com/translate/v2/swagger.yaml#L40

—
Reply to this email directly or view it on GitHub
#35 (comment)
.

[IvanGoncharov]

Problem that I can distinguish between APIs that work with keys and one working without.
So I will add security definition but will make it optional
It's not ideal but definitely step in the right direction.
Sounds good?