Google periodically updates the Health Data API in order to deliver new features and to repair defects discovered in previous versions. In most cases, these changes will be transparent to API developers. However, occasionally we need to make changes that require developers to modify their existing applications.
This page documents any changes made to the Health Data API that may effect your application. We recommend that API developers periodically check this list for any new announcements. Changes will also be announced via this page's Atom feed and the Google Health developers discussion forum.
Features added in this release:
Time to live (auto-expiring) AuthSub session / OAuth access tokens.
The (optional) ttl parameter can be used on the AuthSub or OAuth approval page to request a 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. See the Requesting a token documentation.
Note: This does not apply to single-use (session=0) AuthSub tokens. The Health API does not support temporary tokens.
Category queries now include OR operations. Queries may be reduced to 1 request with this change. See the category queries documentation.
Additional changes made in this release:
Outgoing CCR validates against ccr.xsd. Added <Actor> and <CCRDataObjectID> when necessary. Empty elements are now removed.
Note: This applies to the CCR returned by Google Health. If your application sends invalid CCR data, it will not be reconciled into the users profile.
|
