VICTORY! For me, at least for the SAPISIDHASH that I was looking for was the one that was on the api console. Automation for quite a lot of work, completely legal.
Anyway -> the one I found was SHA1 in the current javascript millisecond tag plus your current SAPISID from your cookie plus domain source
For my request to work, I had to include the following Authorization:SAPISIDHASH 1439879298823_<hidden sha1 hash value> headers in the request Authorization:SAPISIDHASH 1439879298823_<hidden sha1 hash value> as well as X-Origin:https://console.developers.google.com
The first heading, I assume, tells the server your timestamp and the value sha1. The second (breaks if you do not turn it on) reports that the source is used in the sha1 algorithm.
I found an algorithm by digging and debugging hell out of a ton of mini-js NOTE. Between values
Psuedo basiclly code>
sha1(new Date().getTime() + " " + SAPISID + " " + origin)
At least this is how I got my SAPISIDHASH value in my use case here in 2015 (after a few years I know) ... is different from yours, but maybe one day I will help another young good hacker
Dave thomas
source share