Request per hour by API v.14

110723

05-09-2017

Having a request per Hour would optimize a lot the responses because of the large amount of data returned. The functionality is available in v1.3, but it hasn't been provided in the API v1.4. How exist limit of data in return responses, this parameter become very import when is necessary extract informetion that exceed the extraction limits  supported by API.

For exemple:

While we were trying to test version 1.4 API we faced another error:

Scenario tested:

  • Parameters:

{

    "reportDescription":

    {

        "reportSuiteID":"wmbdesktop",

        "reportType":"warehouse",

        "dateFrom":"2016/11/25 09:00:00",

        "dateTo":"2016/11/25 09:59:59",

        "Date_Type":"range",

        "dateGranularity": "hour",

        "source": "warehouse",

        "metrics":[{"id": "visits"}],

        "elements": [{"id":"evar44"}],

        "segment_id":"s2150_5877bf7be4b02fd1c953b4db"

    }

}

Evidence Printscreen:

We have requested in this case an specific period of 1 hour (09am to 9:59:59am).

Unfortunatelly the output is not attending to this period and show us ‘0’ as hour filter.

Even though the period is set as …

1293039_pastedImage_0.png

…the dataset presented is showing us 24 hours (the whole day) of information.

  1293040_pastedImage_1.png

The complete procedure is here:

1293044_pastedImage_3.png

Responses:

1293045_pastedImage_6.png

1293046_pastedImage_8.png

Beacuse of that, the response of the execution is taking too long and 2 pages of data (not as expected).

1293050_pastedImage_9.png

While trying to actually extract the second page the Responses is presenting ‘forever’ the following message: “sending request for repot.get()...” .

No results are returned.

1293051_pastedImage_10.png

Please write back if you have any questions.

1 Comment (1 New)
1 Comment

jen_lasser

Employee

26-07-2019

With the release of 2.0 APIs, 1.4 ideas will be archived.

2.0 API Overview