Getting a 400 error from 1.4 Report.Query endpoint

[doriskuo]

We have recently been getting back 400 status code errors for calls to the 1.4 reporting endpoints that used to work as expected and we hoping we could get some assistance on what might be the cause.

Below you can find an example of our request with some sensitive information redacted. Curious if this could be a side effect of this version of the API nearing EOL. We have implemented the version 2.0 update, but some users prefer 1.4 for its ability to query with multiple dimensions which 2.0 does not provide.

Thanks in advance for any assistance here.

Post Data:

{
    "reportDescription": {
        "reportSuiteID": "[REDACTED]",
        "dateFrom": "2024-09-13",
        "dateTo": "2024-09-18",
        "dateGranularity": "day",
        "metrics": [{
           "id": "revenue"
        }, {
           "id": "orders"
        }, {
            "id": "units"
        }, {
            "id": "visits"
        }],
        "elements": [{
            "id": "lasttouchchannel",
            "everythingElse": true
        }, {
            "id": "evar159",
            "everythingElse": true
        }, {
            "id": "lasttouchchanneldetail",
            "everythingElse": true
        }, {
            "id": "evar21",
            "classification": "UTM Content (v21)",
            "everythingElse": true
        }],
        "segments": null,
        "locale": "en_US",
        "currentData": false,
        "source": "warehouse",
        "elementDataEncoding": "utf8"
    }
}

Endpoint URL: 

https://api.omniture.com/admin/1.4/rest/?method=Report.Queue 

Headers:

Accept:          application/json, text/plain, */*
Content-Type:    application/json
Authorization:   Bearer [REDACTED API TOKEN]
x-api-key:      [REDACTED BUT VERIFIED ACCURATE]
User-Agent:      axios/1.6.7
Content-Length:  544
Accept-Encoding: gzip, compress, deflate, br

[Jennifer_Dungan]

I agree with you on version 1.4 being preferrable for querying multiple dimensions... I am surprised that 1.4 is going to be sunset, since having the two systems running in parallel allows for two very different behaviours (the newer "quick but one dimension", and the older "slower but allows for complex queries"). However, the decision has been made... at least you have 2 years to migrate.

That said, the endpoint should be up and running for the next 2 years, de-commissioning it before the sunset date wouldn't make sense.. there are too many companies still using it....

Now, we don't have any active calls in our system at this time, but I have some old saved Postman queries, so I just gave them a try, and I am getting a 200 response code....

Is this a new API call, or one that has been running for a while?

If it's an established API, then it might just have been a temp issue. If this is new, then you might want to just go with API 2.0 to avoid having to redo all this in 2 years.

If the issue persists, you may have to contact support to look at the logs for your request.