in reply to Re^5: New Bing Search Api (5)
in thread New Bing Search Api (5)

Thanks again for pointing me to the right direction. Adding $req->header('Ocp-Apim-Subscription-Key'=>$BingKey); brings me a bit further. Still something is wrong and the error message is a bit obscure to me.

Connecting to Bing for: https://api.cognitive.microsoft.com/bing/v5.0/ +search?Hello HTTP/1.1 400 Bad Request Cache-Control: private, max-age=0 Date: Mon, 21 Nov 2016 18:39:19 GMT Vary: Accept-Encoding Content-Length: 138 Content-Type: application/json; charset=utf-8 Expires: Mon, 21 Nov 2016 18:38:19 GMT Apim-Request-Id: d3e4c0aa-1a8f-45f4-b3ad-f850296d1651 BingAPIs-Market: de-DE BingAPIs-TraceId: 726DF5B30CE34AF9BBF48A5584E5068C Client-Date: Mon, 21 Nov 2016 18:39:20 GMT Client-Peer: 52.174.60.141:443 Client-Response-Num: 1 Client-SSL-Cert-Issuer: /C=US/ST=Washington/L=Redmond/O=Microsoft Corp +oration/OU=Microsoft IT/CN=Microsoft IT SSL SHA2 Client-SSL-Cert-Subject: /CN=api.cognitive.microsoft.com Client-SSL-Cipher: ECDHE-RSA-AES256-SHA384 Client-SSL-Socket-Class: IO::Socket::SSL P3P: CP="NON UNI COM NAV STA LOC CURa DEVa PSAa PSDa OUR IND" Strict-Transport-Security: max-age=31536000; includeSubDomains; preloa +d X-MSAPI-UserState: eaa0 X-MSEdge-ClientID: 3266EAB9C91A686D383EE36DC87C69F7 X-MSEdge-Ref: Ref A: 726DF5B30CE34AF9BBF48A5584E5068C Ref B: 0E8655691 +1C74DC2F6EACB35EBB37432 Ref C: Mon Nov 21 10:39:19 2016 PST {"_type": "ErrorResponse", "errors": [{"code": "RequestParameterMissin +g", "message": "Required parameter is missing.", "parameter": "q"}]}

Replies are listed 'Best First'.
Re^7: New Bing Search Api (5)
by stevieb (Canon) on Nov 21, 2016 at 18:57 UTC

    Last thing I want to do is read MS Bing documentation, but after a one-second glance, you're missing the very first parameter in the documentation by the looks of it, q:

    Request Parameters q | String | The user's search query
Re^7: New Bing Search Api (5)
by Corion (Patriarch) on Nov 21, 2016 at 19:12 UTC

    If you read the error message, it even tells you what it doesn't like about your request.

    Maybe you want to change your script to remedy the issue the error message points out?