Friday, July 6, 2012

Digest for adsense-api@googlegroups.com - 3 Messages in 2 Topics

Group: http://groups.google.com/group/adsense-api/topics

    veemer <hugh@vmrcommunications.com> Jul 05 09:19AM -0700  

    Belated thanks Sérgio!
     
    On Tuesday, May 1, 2012 12:13:01 PM UTC-5, Sérgio Gomes wrote:

     

    Michael Ormonde <michael.ormonde2@gmail.com> Jul 05 02:23AM -0700  

    Just as an update to this, I tried to submit the post request via a form
    also to ensure my curl request wasn't at fault. Again, I found that I was
    getting the "invalid_scope" response. This didn't happen when I substituted
    the scope for " *https://www.googleapis.com/auth/userinfo.email"; *when I
    used that scope, I was able to complete the authorisation process (although
    obviously that scope isn't useful if I want to access adsense data :)
     
    Michael
     
    On Thursday, 5 July 2012 09:57:10 UTC+1, Michael Ormonde wrote:

     

    Michael Ormonde <michael.ormonde2@gmail.com> Jul 05 03:22AM -0700  

    This may help too. Looks like similar issue reported for the Tasks API...
    Unusual as I had used this flow on the AdSense Managemet API before
    (although that was back in December last year)
     
    https://groups.google.com/forum/?fromgroups#!topic/google-tasks-api/15PxeE89WCo

     
    Again Sergio, I appreciate all the time you're taking to look into this :)
     
    Michael
     
    On Thursday, 5 July 2012 10:23:31 UTC+1, Michael Ormonde wrote:

     

You received this message because you are subscribed to the Google Group adsense-api.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To post to this group, send email to adsense-api@googlegroups.com.
To unsubscribe from this group, send email to adsense-api+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/adsense-api?hl=en.

No comments:

Post a Comment