Hello,

 I am experiencing an issue with paging and startIndex parameters in when making api requests, is there an issue or caviet when making the request I should be aware of?

Currently my requests look like this:

http://api.myspace.com/1.0/people/@me/@all?oauth_consumer_key=xxxxxxxxxxxxxxxxxxxx&oauth_nonce=5008677&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1293033324&oauth_token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&oauth_version=1.0&oauth_signature=xxxxxxxxxxxxxxxxxxxxxxxxxx&startIndex=25&count=25 

When making this request I get a 401 response. However if i omit startIndex and the count params it works, and obviously returns the last/first 20. I have reviewed many posts from developers in the forum and most seem to experiece the same problem. Is this a known issue?

Also when testing I noticed that api requests would randomly throw a 500 error. Is there a page that contains the status of your servers similar to the pages provided by Facebook and Twitter?

Finally I would also like to know if there is a rate limit on the number of requests I can make to your server.

Thank you very much for you help,

Johnny

I spoke to our team, and the startIndex must be in the form of startIndex = (count * i) + 1 where i is any non-negative integer, so if count = 5, startIndex can be 1, 6, 11, 16, etc. That means if you want to have “count=25” then startIndex needs to be 1, 26,51, and so on.

thanks, Joel

Hey Joel,

 Thanks for the information. When I attempted your solution I still recieved a 401 error.

Here is the request:

http://api.myspace.com/1.0/albums/@me/@self?count=25&startIndex=1&oauth_consumer_key=7dfd962acae2450dacca6b512a1ce0cb&oauth_nonce=7113276&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1293113636&oauth_token=mmaHXSDctiEBXEhnTNH4UmMls74e%2FIcuhzK4GvEhEtBByUlnyl%2FxpJJclfaHyEGBaBQo69iQpL3olUfiJf%2FyY80z9glSeN3jSqv2txKurn4%3D&oauth_version=1.0&oauth_signature=IXiVAqlqZhmNUdSLDS7ZXYqmzU0%3d

This is the Respose Header :
The remote server returned an error: (401) Unauthorized.
eedd23ec2926864c79eb5202eac74abb31b537bd070b1dfc
The Dark Side
486
text/html
Thu, 23 Dec 2010 14:14:39 GMT
Microsoft-IIS/7.5

To verify that my access token and secret were still valid I omitted the count=25&startIndex=1 in a following request and the first 20 were returned. I also tested the change when making a request to the Friends API and unfortunately recieved the same result.

 Thanks again,

 Johnny

What was the reason for the 401? It should say. You can send a Wireshark or Fiddler capture to developerrelations@myspace-inc.com if you wish. Thanks!

-Joel

Hey Joel,

 Hope your Holidays are going well. Please see below for the server response:

[truncated] {"statusCode":"401","statusDescription":"Invalid digital signature for base string: \"GET&http%3A%2F%2Fapi.myspace.com%2F1.0%2Fpeople%2F%40me%2F%40all&count%3D25%26oauth_consumer_key%3D7dfd962acae2450dacca6b512a1ce0cb%26oauth_n

I don't know how it is invalid because when count and index params are removed it works.

 I am also sending a wireshark capture of the packets in question. The subject will match this threads title.

Thanks again for your help,

Johnny

Hey Joel,

Are you able to offer any additional guidance?

Thanks,

Johnny

 Almost1 month with no replys. Any hope on a response or direction?

We had some staffing changes, can you please send a Wireshark/Fiddler capture of this issue to developerrelations@myspace-inc.com and include the userID of the user in question as well as the six-digit appID for the app?

thanks,

Joel