Subscription API for heartrate data

[domtwlee]

So I'm all setup with notifications, and was wondering where heartrates are categorized under in regards to the collectionType for notifications? Are they under activities? if so, how would you know which endpoint to fetch data from, given that activities is a fairly broad category.

for example, how would the payload below indicate that it's heartrates? 

{
  collectionType: "activities",

  date: "2020-01-01",
  ownerId: "abc",
  ownerType: "user",

  subscriptionId: "12345"
}

Thanks, hope to get a reply soon.

[Gordon-C · Accepted solution]

Hi @domtwlee

Heart rate is part of the activities collection.  At this time, we do not provide detailed information on what information changed, but we do have an enhancement request to provide this information.  Right now, if you're collecting heart rate, the new heart rate data would be available each time an activity notification is sent to you.  You'll also have to check the activity endpoints to see if there is new activity data to retrieve.  Keep in mind, the calories data is also part of the activities endpoints and collection.  If the user enables the activities scope but not heart rate you'll receive a notification every time the user syncs noting updated calories burned data, even if there wasn't an activity.

If the mobile application is running on their device, the device will sync every 15 minutes.  At most, you shouldn't get more than 4 activity notifications per hour.

[domtwlee]

Got it, thanks for the quick response. I look forward to the enhancement request.