Hi Brad, The AuthSub session token is a random alphanumeric sequence that can also include hyphens and underscores. Once a user has authorized the link between your application and Health, you'll want to retain to session token for future requests. Each session token is associate with an individual user profile, so it is a unique identifier for a user's record in Health. Each CCR record imported into Health should contain data for a single individual. Therefore, if you want to import data for multiple Health users, you will need to construct and send multiple CCR records, and will need to include each user's AuthSub session token.
I hope this clarifies! I've CC'd the Google Health Developers' group, which is the perfect forum for such questions. Paul (Google) On Jun 1, 2:32 pm, DraperB wrote: > What is the format of the long-lived session token? > > How, other than by name, do we identify a member in a CCR record? By > long-lived token? -- 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.
