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

Thank you for your answer. Here you can find a complete (and slightly modified) script for what I am trying to do. Api Key is not provided. If the script gets a response, it should enter the intended subrutine and I should see my nice message "I could connect to the API" and smile. But I can't get any response, so I get "Impossible retrieving info from Web".

#!/usr/bin/perl

use strict;
use warnings;
use LWP::UserAgent;
use JSON;

my $BingKey="xxx";
my $MyBingJsonQuery = "Hello";


    my $href= 'https://api.cognitive.microsoft.com/bing/v5.0/search?' 
+. $MyBingJsonQuery;
    print "Connecting to Bing for: $href\n";
    my $ua= LWP::UserAgent->new();

    my $req = HTTP::Request->new(GET => $href);
    $req->header($BingKey);
    my $res = $ua->request($req);
    
  # Check the outcome of the response
  if ($res->is_success) {
    print "I could connect to the API\n";
     my $resp= $ua->get($href);
    my $data = decode_json($resp->content); 
    my @urls = map { $_->{'Url'} } @{ $data->{d}->{results} };
  }
  else {
    print "Impossible retrieving info from Web\n";
  }

[download]

Replies are listed 'Best First'.
Re^3: New Bing Search Api (5)
by Corion (Patriarch) on Nov 21, 2016 at 18:05 UTC

    Have you read the documentation you linked to?

    It also shows you what kinds of errors the API could return.

    Maybe you want to show us what exact kind of error you get back?

    Printing out the full response might show you something that corresponds with the error types of the API:

    print $res->as_string;

    [download]

    Maybe now is a good time to learn about HTTP and status codes and what the stuff in HTTP::Message and HTTP::Response is all about.

[reply]
[d/l]

      Okay. I get an error message. New lesson for me. The error seems to point to my suspect. I am not passing correctly the parameters...

      HTTP/1.1 401 Access Denied
Date: Mon, 21 Nov 2016 18:16:11 GMT
WWW-Authenticate: AzureApiManagementKey realm="https://api.cognitive.m
+icrosoft.com/bing/v5.0",name="Ocp-Apim-Subscription-Key",type="header
+"
Content-Length: 152
Content-Type: application/json
Apim-Request-Id: a4599b0f-4402-46cd-9f3d-2d1e0f1f0199
Client-Date: Mon, 21 Nov 2016 18:16:12 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
Client-Warning: Unsupported authentication scheme 'azureapimanagementk
+ey'
Strict-Transport-Security: max-age=31536000; includeSubDomains; preloa
+d

{ "statusCode": 401, "message": "Access denied due to missing subscrip
+tion key. Make sure to include subscription key when making requests 
+to an API." }

      [download]
[reply]
[d/l]

        Maybe now is a good moment to revisit the Microsoft documentation you already linked and my first reply, both of which mention Ocp-Apim-Subscription-Key, which is missing from all your code. Note that the WWW-Authenticate header you get back also shows that header name.

        Most likely the correct approach is to add a header with that name and your secret key as the value.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom