Time to live (auto-expiring) AuthSub session / OAuth access tokens: http://code.google.com/apis/health/docs/2.0/developers_guide_protocol.html#AuthSubRequestToken
By using the new (optional) ttl parameter on the AuthSub or OAuth approval page, third parties can request a session token that expires in a specified amount of time. This is useful for services that need to push/pull data rarely and have little need for a token that never expires. Note: This does not apply to single-use (session=0) AuthSub tokens. Health does not support temporary tokens. --- Category queries now include ORing operations http://code.google.com/apis/health/docs/2.0/reference.html#CatQueries This is useful for apps which query for multiple category names. Queries may be reduced to 1 request with this change. A few examples: The user's conditions OR medications GET /-/medication%|condition All conditions that are either named "Calf Pain" OR "Cough": GET /-/condition/{http://schemas.google.com/health/item}Calf+Pain| {http://schemas.google.com/health/item}Cough --- Outgoing CCR validates against ccr.xsd. -- added actor and CCRDataObjectID when necessary. -- remove empty elements. Note: This applies to the CCR returned by Google Health. If your application sends invalid CCR, it will not be reconciled into the users profile. Eric --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
