Get IRN Alerts List returning data in a format differing from the past and Example Response

[rbcunningham]

I have use "Get IRN Alerts List" extensively this year, with the data formatted as show in the example response:

"alerts": [
    {
      "alertTime": "yyyy-mm-ddTHH:MM:SS",
      "detectedTime": "yyyy-mm-ddTHH:MM:SS",
      "serviceVersion": "2.2",
      "algoVersion": "1.6",
      "deviceType": "Sense",
      "windows": [
        {
          "startTime": "yyyy-mm-ddTHH:MM:SS",
          "bpmData": [
            {
              "dataTime": "yyyy-mm-ddTHH:MM:SS",
              "value": 73
            }
          ]
        }
      ]
    }
  ]...

Starting in September, the Web API returns the data in a format without alert metadata and bpm values, even for dates that returned the documented format before.  Here is an example fragment:
{
"alerts": [
{
"windows": [
{
"bpmData": [
{
"time": "yyyy-mm-ddTHH:MM:SS"
},
{
"time": "yyyy-mm-ddTHH:MM:SS"
},
{
"time": "yyyy-mm-ddTHH:MM:SS"
}...

How can I ger the IRN data in the format as shown in the Example Response?

[GordonFitbit]

Hi @rbcunningham 

Since the historical data is not appearing anymore, I think this problem is related to a change in the service.  Let me check with engineering and I'll report back to you.

Gordon

[GordonFitbit]

Hi @rbcunningham 

This problem should be fixed, now.  Would you please try calling the endpoint to see if you get the necessary data?

[rbcunningham]

Thanks, the endpoint works when I call it from my app.

FYI: I tested the endpoint from https://dev.fitbit.com/build/reference/web-api/troubleshooting-guide/oauth2-tutorial/ and got the incorrectly formatted results I put in my original post.

[GordonFitbit]

Thanks for confirming.  The oauth2 tutorial is just a tool for testing the oauth2 flow.  It's not really meant to test the endpoints.