Hi Shrenik, That looks correct; although, you'll need to replace "profileID" with the random looking, alpha-numeric string that you get from the profile list feed. A real URL will look more like the following:
https://www.google.com/health/feeds/profile/ui/8qdQbFaFI8U?digest=true Paul S. On Tue, May 18, 2010 at 6:57 AM, Shrenik Vikam <[email protected]>wrote: > is following is the correct url for HTTPGET ? > "https://www.google.com/health/feeds/profile/ui/profileID?digest=true"; > > > On May 17, 9:29 pm, "Paul (Google)" <[email protected]> wrote: > > Hello Shrenik, > > > > Once your user has authenticated, you'll need the id of the profile > > that the user wants to access, since one account can have multiple > > profiles. To get a list of ids, you'll want to use the "profile list" > > feed of the ClientLogin API, which is described at the following > > location. > > > > http://code.google.com/apis/health/docs/2.0/reference.html#ClientLogi... > > > > One you have the id for the profile that the user is interested in, > > you'll need to use it for the ClientLogin "profile feed", which is the > > second URL listed at the above location. > > > > By default, the profile feed will return a list of records, or CCR > > documents, that have been added to the profile. To get all of the > > records in a single CCR document, you can append "?digest=true" to the > > profile feed URL. The digest parameter is described at the following > > location: > > > > http://code.google.com/apis/health/docs/2.0/reference.html#DigParam > > > > Thanks for your question! Certainly let us know how it goes! > > > > Cheers! > > > > Paul > > > > On May 14, 4:43 am, Shrenik Vikam <[email protected]> wrote: > > > > > I am using clientlogin method to communicate > > > I want to get all record of a particular profile > > > how do I get that ? > > > > > Thanks in advance > > > Shrenik > > > > > -- > > > 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]<googlehealthdevelopers%[email protected]> > . > > > For more options, visit this group athttp:// > groups.google.com/group/googlehealthdevelopers?hl=en. > > > > -- > > 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]<googlehealthdevelopers%[email protected]> > . > > For more options, visit this group athttp:// > groups.google.com/group/googlehealthdevelopers?hl=en. > > -- > 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]<googlehealthdevelopers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/googlehealthdevelopers?hl=en. > > -- 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.
