I'm getting 409 response code when sending notification via REST API for a one app, for other apps everything is ok, notifications are send without problem.

 errormessage -

The page was not displayed because there was a conflict.

 There were some intermittent issues due to configuration changes, but these 409's should go away now.

thanks,

Joel

But i still get the same 409 .. my app is http://www.myspace.com/330787305 please check if it possible

Thanks,

Artavazd

 Hi,

We have some updated API docs which you should peruse. It might help with the problems you're having.

http://wiki.developer.myspace.com/index.php?title=Category:OpenSocial_v0.9_REST_Resources

If you get a 409 with the new api, please post exactly what you did so I can attempt to replicate the errors.

thanks,

Joel

Hi Joel,

I also get 409 response with the new API. When I make GET request to http://opensocial.myspace.com/roa/09/albums/@me/@self with all the oauth parameters, I get {"statusCode":"409","statusDescription":"Unexpected error occurred."} as response. I tried with Myspace Oauth testing tool as well and it returns the same.

Could you please help me with it?

Regards,

Priyanshu

 Please send a Fiddler or Wireshark capture of the communication to developerrelations@myspace-inc.com. Please include the six digit appID, the consumer key, and the consumer secret.

thanks,

Joel

 Hi Joel,

I have sent the wireshark capture. Let me know if you find something.

 Regards,

Priyanshu

 Our team examined your error, and replied to your message.

thanks,

Joel

Obviously because some issues deal with private information like consumer keys/secrets along with other things, which is why these issues are handled privately.

-Joel

I think it is possible to bring down the api by using parameters that are not defined. By "bringing down" I mean it will just reply 409 and no data. I think I've achieved this through a call to the search interface like:

 http://api.myspace.com/opensearch/people?searchTerms=trailerpark&format=xml?test

You will notice that it has a surplus "?test" at the end.

 I've informed our team about this weakness. They're working on a solution which will result in more graceful error messages.

thanks,

Joel