SecurityDefinitions missing

[maryguirola]

There are some APIs without security definitions and actually they needed. Here is the list: Requires API key:

• Zoom Connect
• Watchful.li
• Versioneye
• Spectrocoin
• Peel Tune
• ~~Gennea~~
• ~~Statsocial~~

Requires OAuth 2.0:

• Uploady

Basic authentication:

• ~~Geodesystems~~

Others:

• Discovery Market Research
• Glugbot
• Datumbox
• Daisycon
• Clarify
• Blackberry
• Beanstream
• Infermedica

[sanchojaf]

@IvanGoncharov if is possible, could you review the comment added by @maryguirola, in order to know if we can help you fixing some of this specs without security definitions or if you will fix automatically with your script.

[IvanGoncharov]

@maryguirola @sanchojaf Yes definitely, I highly appreciate your help. All APIs in the list are ready for the fix. except these:

• Datum - has api_key marked but it inside formData and it not supported by swagger
• Uploady - I couldn't update this API because of #40
• Daisycon - the same #40

If you have a link to documentation explaining security mechanism for this API please make a comment, something like #According to <URL>. It's optional so if don't have a good link or it described in description of Swagger file you can skip it. YAML support comments, everything starting with # is a comment.

Please make the first PR with one API so we can solve all technical issues.

[sanchojaf]

@IvanGoncharov only for be sure, you say that we can add a first PR for any API in the list, except (Datum, Uploady and Daisycon), is that right?

[IvanGoncharov]

@sanchojaf @maryguirola Yes, any of them except these three.

[IvanGoncharov]

@maryguirola I crossed out fixed APIs from your initial comment.