Getting "Invalid API Key"

[jagannath]

Hi,

After getting successful access token and secret, trying get
rummble services. But every time getting error "Invalid API Key". If
anyone knows the solution, please share with me.

Below is the captured Ethereal packet. If in the request any problem,
let me know.
Though I am an active developer, still getting "X-Mashery-Error-Code:
ERR_403_DEVELOPER_INACTIVE" in the response header. If this error is
the reason for getting error "Invalid API Key", please tell me what to
do from my side.

GET /?format=xml&method=user%2EgetInfo HTTP/1.1
Host: api.rummble.com
Authorization: OAuth realm="",
oauth_consumer_key="x6vh68q6yxqyc5mcbmrqmfkn",
oauth_token="2e03be4760ea09e860f9a7b90eef4e84",
oauth_signature_method="HMAC-SHA1", oauth_nonce="2587802033",
oauth_timestamp="1279638217", oauth_version="1.0",
oauth_signature="Ero3GjSfERTMm126AG6v2nldJYk%3D"

HTTP/1.1 200 OK
X-Mashery-Responder: proxyworker-i-6866f301.mashery.com
X-Mashery-Error-Code: ERR_403_DEVELOPER_INACTIVE
Content-Type: text/xml
Accept-Ranges: bytes
Content-Length: 85
Date: Tue, 20 Jul 2010 06:03:54 GMT
Server: Mashery Proxy

<response status="fail"><code>100</code><message>Invalid API Key</
message></response>

Thanks in Advance.
Jagannath

[Clive Cox]

It may be because a present limitation of our API proxy Mashery, which
doesn't handle OAUTH parameters in the HTTP header. If you could send
them as normal HTTP parameters and see if you still get the problem?

Clive

[jagann...@gmail.com]

Hi Clive,

 

 Thanks for your valuable suggestion.

 

 As per your suggestion, I removed OAUTH parameters in HTTP header and send as normal HTTP parameters.

 Still getging the same problem.

  Captured Ethereal Packets:

  GET /?method=user%2EgetInfo&oauth%5Fnonce=3601326724&oauth%5Fconsumer%5Fkey=x6vh68q6yxqyc5mcbmrqmfkn&oauth%5Ftimestamp=1279815274&oauth%5Ftoken=e36fefaaf2ab860f3f7cce554a602668&oauth%5Fsignature%5Fmethod=HMAC%2DSHA1&format=xml&oauth%5Fversion=1%2E0&oauth%5Fsignature=17lcwls%2FXKiTKTLsnlYVcS7E7Ww%3D HTTP/1.1

Host: api.rummble.com

 

HTTP/1.1 200 OK

X-Mashery-Responder: proxyworker-i-6866f301.mashery.com

X-Mashery-Error-Code: ERR_403_DEVELOPER_INACTIVE

Content-Type: text/xml

Accept-Ranges: bytes

Content-Length: 85

Date: Thu, 22 Jul 2010 07:15:11 GMT

Server: Mashery Proxy

 

<response status="fail"><code>100</code><message>Invalid API Key</message></response>

 

Thanks & Regards,

K. Jagannath Rao

 

 

--
You received this message because you are subscribed to the Google
Groups "Rummble API" group.
To post to this group, send email to rummb...@googlegroups.com
To unsubscribe from this group, send email to
rummble-api...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rummble-api?hl=en
For API Documentation, visit http://developer.rummble.com/docs

--
Regards,
K.Jagannath Rao

[Clive Cox]

Just to say we have made a change with our API proxy which means OAuth
parameters in the HTTP Header will now work as expected.

Clive

> > rummble-api...@googlegroups.com<rummble-api%2Bunsu...@googlegroups.com>

> > For more options, visit this group at
> >http://groups.google.com/group/rummble-api?hl=en

> > For API Documentation, visithttp://developer.rummble.com/docs
>
> --
> Regards,
> K.Jagannath Rao

[jagann...@gmail.com]

Hi Clive,

   Thanks for your information. I am getting proper response from rummble api server after making HTTP POST. But removed the OAUTH parameters in HTTP header and make all parameter as part of HTTP body. I will check with OAuth parameters in the HTTP Header and will let you know the result soon

Thanks and Regards,
K. Jagannath Rao

For API Documentation, visit http://developer.rummble.com/docs

--
Regards,
K.Jagannath Rao