Get an authorization code from Google

curl -s -d Email=$email -d Passwd=$password -d service=lh2 | grep Auth | sed 's/Auth=\(.*\)/\1/'
This is a basis for other Google API commands.

What Others Think

Try this example: Please define $youremail, $yourpassword, $contactemail. curl -s -H "Content-Type: application/atom+xml" -d "<atom:entry xmlns:atom='' xmlns:gd=''><atom:category scheme='' term='' /><gd:email rel='' address='$contactemail' /></atom:entry>" -H "Authorization: GoogleLogin auth=$(curl -s -d Email=$youremail -d Passwd=$yourpassword -d service=cp | grep Auth | sed 's/Auth=\(.*\)/\1/')" ""
matthewbauer · 593 weeks and 5 days ago
On behalf of Google, we recommend that somebody make an alternative in OAuth2. ClientLogin is now deprecated.
kendfinger · 510 weeks and 1 day ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: