Expand my Community achievements bar.

SOLVED

Help with reporting API v2.0

Avatar

Level 1

Hi.

 

We are experiencing issues with reporting API v2.0. The error is:

 

{
"errorCode": "resource_not_found",
"errorDescription": "Requested resource URL or path does not exist. requestUrl=http://appservice5.omniture.com/analytics/1.0/ exceptionMessage=HTTP 404 Not Found",
"errorId": "86b84583-a125-4d28-8627-7045e72a7ed5"
}

 

Can you help us?

1 Accepted Solution

Avatar

Correct answer by
Community Advisor and Adobe Champion

Wondering where you get the http://appservice5.omniture.com. But according to the API documentations, the API v2.0 should be starting with https://analytics.adobe.io, like the discovery API, https://developer.adobe.com/analytics-apis/docs/2.0/guides/endpoints/discovery/

View solution in original post

3 Replies

Avatar

Level 1

We are having the same issue. Most endpoints give us the same error but authentication and dimensions endpoints are working ... weird.

Avatar

Correct answer by
Community Advisor and Adobe Champion

Wondering where you get the http://appservice5.omniture.com. But according to the API documentations, the API v2.0 should be starting with https://analytics.adobe.io, like the discovery API, https://developer.adobe.com/analytics-apis/docs/2.0/guides/endpoints/discovery/

Avatar

Level 1

Maybe I should have been more explicit:

 

request: 

 

curl --location --request POST 'https://analytics.adobe.io/api/{company_id}/reports' \
--header 'x-api-key: {api_key}' \
--header 'Authorization: Bearer {token}' \
--header 'x-proxy-global-company-id: {company_id}' \
--header 'Content-Type: application/json' \
--data-raw '{report}'
 
reponse:
{
"errorCode": "resource_not_found",
"errorDescription": "Requested resource URL or path does not exist. requestUrl=http://appservice5.omniture.com/analytics/1.0/ exceptionMessage=HTTP 404 Not Found",
"errorId": "86b84583-a125-4d28-8627-7045e72a7ed5"
}
 
Such behaviour was present the entire day of Fri. 27.01.2023. Currently is working, so that is why I believe the issue was present with Adobe.