API 403

[jparicka]

[ jparicka dev ~/social ] wget "http://services.digg.com/search/
stories?query=currency&sort=digg_count-desc&appkey=http%3A%2F
%2Ftest&type=json

Resolving services.digg.com... 64.191.203.26
Connecting to services.digg.com|64.191.203.26|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
19:48:23 ERROR 403: Forbidden.

How can I have my IP addresses white-listed?

Thank you,

Jan

[Steve Williams]

At 07:57 PM 10/19/2009, jparicka wrote:
>/search/stories?query=currency&sort=digg_count-desc&appkey=http%3A%2F%2Ftest&type=json

Interesting. I tried that request with wget and an HTTP 1.0
client. Both got 200 responses with valid JSON.

Do you see the 403 consistently or intermittently?

>How can I have my IP addresses white-listed?

It may not be the IP address, but you can send it to me in a private
email. I'll have ops check.

[Jan Paricka]

Hi Steve,

At 07:57 PM 10/19/2009, jparicka wrote:
>/search/stories?query=currency&sort=digg_count-desc&appkey=http%3A%2F%2Ftest&type=json

Interesting.  I tried that request with wget and an HTTP 1.0
client.  Both got 200 responses with valid JSON.

Do you see the 403 consistently or intermittently?

I have problems accessing the API from all our machines hosted in GoGrid.

 

>How can I have my IP addresses white-listed?

It may not be the IP address, but you can send it to me in a private
email.  I'll have ops check.

Will do.

Thank you,

Jan

 

--
Jan Paricka

Let's stay in touch via LinkedIn:
http://www.linkedin.com/in/jparicka

[Steve Williams]

Jan, thanks for sending your IP addresses and appkey. Our ops folks
tell me that neither is blocked, so the 403 is for some other reason.

Please look at the document returned with the 403 response. There
should be a message in the document with a bit more info.

For example, here's a request with an invalid appkey:

/stories?appkey=blah&type=json

The document returned with the 403 response:

{"timestamp":1256056568,"code":1028,"message":"Invalid application key"}

That doesn't apply to you, because your appkey is valid.

Here's a request with no appkey:

/stories?type=json

The response:

{"timestamp":1256056655,"code":1005,"message":"Application key required"}

Again, that doesn't apply to you.

Your original message showed a wget command. Is your wget configured
to send a User-agent header? Digg requires it.

http://apidoc.digg.com/BasicConcepts#UserAgents

What environment does your application use? Does your application
send the User-agent header?