We just wanted to give the development community a heads-up on two changes to our legacy REST APIs we will be making to the platform in the coming weeks. Neither will require any changes on your part. The goal of the changes is to make sure developers have a consistent experience accessing the legacy (v1/v2) REST endpoints with the current OpenSocial 1.0 APIs.
The first change we are making is to reuse the code to compute and validate OAuth digital signatures that exists in the OpenSocial 1.0 APIs, in the legacy v1/v2 REST endpoints. OAuth signed requests should work consistently regardless of what endpoint you are requesting.
The second change is related to privacy bugs in the legacy endpoints. The legacy endpoints will now perform the same permissions checks as the OpenSocial 1.0 APIs. For example, profile requests in v1/v2 will check the same user permissions that the OpenSocial person endpoint does. You should expect the legacy endpoints to work the same as the current OpenSocial 1.0 endpoints, but we highly encourage you to code to the OpenSocial 1.0 endpoints and consider the legacy REST APIs deprecated.
Again, developers should not have to make any changes to continue using the Myspace Developer Platform, but we just wanted to let you know what’s coming. As always, please let us know if anything seems incorrect or needs improving. We’d love to hear from you.
Myspace Developer Platform