@EaglePtPartners: We’ve taken a closer look at these requests and they’re actually the identical—they use the same param values. Could you please clarify which request is causing problems?
In any case, looking at the response output, we can tell this came from a request to the GET /1/stats/jobs/accounts/:account_id endpoint—see "data_type": "job".
An example POST /1/stats/jobs/accounts/:account_id response (after going through the async flow, including downloading .gz file) looks like this (see "data_type": "stats"):
$ twurl -X POST -H ads-api.twitter.com "/1/stats/jobs/accounts/18ce54h6gph?entity=LINE_ITEM&entity_ids=89jlk&start_time=2017-03-28T00:00:00Z&end_time=2017-03-30T00:00:00Z&granularity=TOTAL&placement=ALL_ON_TWITTER&metric_groups=ENGAGEMENT"
{
"data_type": "stats",
"time_series_length": 1,
"data": [
{
"id": "89jlk",
"id_data": [
{
"segment": null,
"metrics": {
"impressions": [
1011
],
"tweets_send": null,
"qualified_impressions": null,
"follows": null,
"app_clicks": null,
"retweets": null,
"likes": null,
"engagements": [
17
],
"clicks": [
17
],
"card_engagements": null,
"replies": null,
"url_clicks": [
6
],
"carousel_swipes": null
}
}
]
}
],
"request": {
"params": {
"start_time": "2017-03-28T00:00:00Z",
"segmentation_type": null,
"entity_ids": [
"89jlk"
],
"end_time": "2017-03-30T00:00:00Z",
"country": null,
"placement": "ALL_ON_TWITTER",
"granularity": "TOTAL",
"entity": "LINE_ITEM",
"platform": null,
"metric_groups": [
"ENGAGEMENT"
]
}
}
}
Hope this helps!
