Thanks for all of your help Paul. As you suggested, I was looking for
data on the live system using H9 credentials. Correcting this solved
everything.

On Jul 30, 3:51 pm, "Paul (Google)" <[email protected]> wrote:
> Hi Art,
>
> When you're authenticated via ClientLogin, you have access to all of
> the profiles managed by a single account; however, each profile has a
> separate id that must be used after to "ui" path in the request URL in
> order to access the data in a particular profile.  You can receive the
> profile names and corresponding ids using the profile list feed, which
> is documented at the following location.
>
> http://code.google.com/apis/health/docs/2.0/reference.html#ClientLogi...
>
> You can also see the profile ids in the browser location bar by
> clicking on the profile name on the left side of the UI.  For the
> request you're sending, are you certain that the profile associated
> with the id you're sending has data loaded?
>
> Paul
>
> On Jul 28, 4:21 pm, art <[email protected]> wrote:
>
>
>
> > Hi Paul,
>
> > Thanks so much for your prompt response. I had actually tried the URL
> > you suggested and it technically succeeds but it's not actually
> > dumping any of the data from the profile.
>
> > The feed result I get:
>
> > <feed xmlns='http://www.w3.org/2005/Atom'xmlns:openSearch='http://
> > a9.com/-/spec/opensearch/1.1/' xmlns:ccr='urn:astm-org:CCR'
> > xmlns:batch='http://schemas.google.com/gdata/batch'xmlns:h9m='http://
> > schemas.google.com/health/metadata' xmlns:gd='http://
> > schemas.google.com/g/2005' gd:etag='W/&quot;YDwqeyI.&quot;'>
> > <id>https://www.google.com/h9/feeds/profile/ui/XXXXXXXXXXX</id>
> > <updated>1970-01-01T00:00:00.000Z</updated>
> > <category scheme='http://schemas.google.com/g/2005#kind'term='http://
> > schemas.google.com/health/kinds#profile'/>
> > <title>Profile Feed</title>
> > <link rel='http://schemas.google.com/g/2005#feed'type='application/
> > atom+xml' href='https://www.google.com/h9/feeds/profile/ui/
> > XXXXXXXXXXX'/>
> > <link rel='http://schemas.google.com/g/2005#post'type='application/
> > atom+xml' href='https://www.google.com/h9/feeds/profile/ui/
> > XXXXXXXXXXX'/>
> > <link rel='http://schemas.google.com/g/2005#batch'type='application/
> > atom+xml' href='https://www.google.com/h9/feeds/profile/ui/XXXXXXXXXXX/
> > batch'/>
> > <link rel='self' type='application/atom+xml' 
> > href='https://www.google.com/h9/feeds/profile/ui/XXXXXXXXXXX?digest=true'/>
> > <author><name>Google Health</name></author>
> > <openSearch:startIndex>1</openSearch:startIndex>
> > </feed>
>
> > One other question if you don't mind: When a profile is shared with
> > another Google Health member, does that sharing only include web
> > access and not api access?
>
> > Thanks!
>
> > --Art
>
> > On Jul 28, 11:46 am, "Paul (Google)" <[email protected]> wrote:
>
> > > Hi Art,
>
> > > You can use the "digest=true" parameter with the ClientLogin profile
> > > feed to retrieve a digest of entries.  Your request URL would look
> > > like the following:
>
> > >https://www.google.com/h9/feeds/profile/ui/<profile_id>?digest=true
>
> > > The ClientLogin feeds have the "ui" path in them in order to specify
> > > which profile you're accessing.  There's more information on the
> > > ClientLogin feeds at following location:
>
> > >http://code.google.com/apis/health/docs/2.0/reference.html#ClientLogi...
>
> > > I hope this helps!
>
> > > Paul (Google)
>
> > > On Jul 27, 4:40 pm, art <[email protected]> wrote:
>
> > > > I see how to do this using 
> > > > AuthSub:https://www.google.com/h9/feeds/profile/default?digest=true
>
> > > > but I don't see how to do it using ClientLogin (I've already got my
> > > > profile ID).
>
> > > > Any help is much appreciated, thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Health Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/googlehealthdevelopers?hl=en.

Reply via email to