Server protocol signing changes
April 7th, 2009 | Published in Google Orkut
For developers using the REST and RPC endpoints to access the social data on orkut, we'd like to announce the following alterations we've made to the underlying implementation:
- We now require the content-type header of the requests to be application/json instead of application/x-www-form-urlencoded
- We have added a new method for signing the request using body hashes.
As always, if you have any questions or just want to chat about the platform, the developer forum is always available.