"403 Forbidden" is they will be displayed in the "API"

[yamayamax]

Nice to meet you.
Although the future API of the question of "URL Metrics", I want you to forgive me English is very immature thing.

I'm very troubled now.
If you call the "API" in the manner described below, such PHP of the program, "403 Forbidden" is the result.
Because the information when you visit the URL directly is displayed, we suspect the PHP of the problem.
About the cause, it will be saved in a very and Nowak advice.
Whether Thank you.

code

$accessID = "<removed for="" privacy="">";
$secretKey = "<removed for="" privacy="">";
$expires = time() + 300;
$SignInStr = $accessID. "\n" .$expires;
$binarySignature = hash_hmac('sha1', $SignInStr, $secretKey, true);
$SafeSignature = urlencode(base64_encode($binarySignature));
$objURL = "http://www.google.com";
$flags = "103079217188";
$reqUrl = "http://lsapi.seomoz.com/linkscape/url-metrics/".urlencode($objURL)."?Cols=".$cols."&AccessID=".$accessID."&Expires=".$expires."&Signature=".$SafeSignature;
$opts = array(CURLOPT_RETURNTRANSFER => true);
$curlhandle = curl_init($reqUrl);
curl_setopt_array($curlhandle, $opts);
$content = curl_exec($curlhandle);
curl_close($curlhandle);
$resObj = json_decode($content); //decode the json object and fetch results
echo $reqUrl . "
";
echo "Domain Authority : " . $resObj->{'pda'};
echo "Page Authority : " . $resObj->{'upa'};
?>
------------------------------------------------------------------------------------</removed></removed>

[JordanRailsback]

It's no trouble at all, yamayamax! Happy to help any time

[yamayamax]

Thank you, "Jordan Railsback" Mr.
Sorry, I did not notice the place to ask questions.

Try to question in the coming "Mozscape Developer Discussion Group".
We will try to also check the "help@moz.com"
(It is really a simultaneous breach of manners in my country)

Thank you for your kindness!

[JordanRailsback]

Hi there!
While I'm afraid I'm not able to help troubleshoot the code that's generating the call you're having trouble with, perhaps the folks over on our Mozscape Developer Discussion Group would be able to!

If you'd like to either drop an example call in here or send a sample call over to help@moz.com, I can certainly help identify what call parameters might be causing the 403 response for that specific call.