Seeing 404s when calling https://api.omniture.com/admin/1.4/rest/ Classifications.CreateImport

[AkshaySh6]

Hello,

We have an Adobe integration which is failing when calling the https://api.omniture.com/admin/1.4/rest/ with the Classifications.CreateImport method. The report suite and list variable used in the request are both correct. Has anybody seen other reasons for such requests to return 404s?

I'm at a loss about what this could be about. It doesn't appear to be about authorization/authentication and this is clearly an end point that exists and works for other integrations. Are there other potential reasons for the 404s?

Regards,

Akshay 

[Jennifer_Dungan]

In the GitHub swagger, https://api.omniture.com/admin/1.4/rest/?method=Classifications.CreateImport appears to be returning a non-404 status code... now, loading this directly (with no authentication) is returning a 400 "Bad Request" which is understandable... but it's not a 404.

Since I cannot see your full request, I think you would be best to contact Client Care as they will be able to diagnose connection issues better than anyone here.

One more point though... as much as I prefer API 1.4 over 2.0... 1.4 is now slated for being sunset in 2026.. so it might be in your best interest to work on integrating the 2.0 API rather than an API which has limited life left... 

[AkshaySh6]

Hello Jennifer,

Thanks for your response! 

This is the request: {\"url\":\"https://api.omniture.com/admin/1.4/rest/\",\"method\":\"POST\",\"headers\":{},\"query\":{\"method\":\"Classifications.CreateImport\"},\"body\":{\"rsid_list\":[\"<report suite name>\"],\"element\":\"listvar2\",\"email_address\":\"noreply@example.com\",\"header\":[\"Key\",\"Survey\",\"Question\",\"Response\",\"Survey > Question > Response\"],\"overwrite_conflicts\":1}}

Does anything about the above look off to you?

I have never contacted Client Care before, is there a direct link through which to do that?

Thanks for bringing up the 1.4 api sunset, we are aware of this and will work towards sunsetting out 1.4 api sometime in 2025 but this particular issue shouldn't be related to the api version from what I can tell. We have multiple other integrations that work without any issues. This particular integration is running into these persistent 404s

[Jennifer_Dungan]

Hi, first, sorry for the late response.

I nothing immediately pops out to me... I am more familiar with the curl syntax shown in the examples, but I would expect the JSON to work as well.

Client Care has been moved to the Admin Console.... so people with the rights to contact support should have the option in their menu

Glad to know you are aware of the sunset, I didn't want you to be caught off guard.