Campaign Manager 360 API Python Script

431 views
Skip to first unread message

CW LEE

unread,
Aug 25, 2021, 1:05:03 AM8/25/21
to Google's Campaign Manager 360 API Forum
After i get the profile ID successfully,  I obtain the issue which is 

googleapiclient.errors.HttpError: <HttpError 404 when requesting https://dfareporting.googleapis.com/dfareporting/v3.4/userprofiles/xxxxx/reports/xxxx/run?alt=json returned "Not Found". Details: "[{'message': 'Not Found', 'domain': 'global', 'reason': 'notFound'}]">

Would it be this service account don't have any report? And I need to share it to service account?
Do I need to anything else? Thanks.

DCM API (DoubleClick Campaign Mgr)

unread,
Aug 25, 2021, 5:23:12 AM8/25/21
to jessi...@fabcom.hk, google-doubleclick-...@googlegroups.com

Hi CW LEE,

 

Thank you for reaching out to us.

 

Could you please share with us the following information?

  • DCM Account ID
  • Profile ID used in API call
  • Report ID used in API call
  • Request URL with visible param values
  • Full screenshot of the API Response (the shared API response does not seem complete)
Regards,
Google Logo
Michael Angelo Legaspi
DCM API Team
 


ref:_00D1U1174p._5004Q2MiaID:ref

CW LEE

unread,
Aug 25, 2021, 5:43:37 AM8/25/21
to Google's Campaign Manager 360 API Forum
DCM Account ID: 466001
PROFILE_ID: 841254622 (me), 6828635 (Service Account)
REPORT_ID: 6593001
utils.py
main - Copy.py

DCM API (DoubleClick Campaign Mgr)

unread,
Aug 26, 2021, 1:20:37 AM8/26/21
to jessi...@fabcom.hk, google-doubleclick-...@googlegroups.com

Hi CW LEE,

 

Thank you for your response.

 

However, I'm afraid I do not see existence of the given profile IDs (841254622, 6828635) that is supposedly associated with this DCM Account ID: 466001. Would you please double check this on your end if you shared the correct profile IDs in making API calls?

 

On the other hand, we can only respond with API perspective, thus we cannot really see through your code the requested API call details. Could you please share with us again the following?

  • Request body & URL you are trying to access with param values
  • API Response in JSON Format

 

This should be similar to your shared information on your original post but with more details. Specifically on the URL, not blinding the important ones like profile ID and report ID in path parameter, as well as the complete detail on the API response.

In summary so far, if you are indeed passing the incorrect information to the request URL, then it is most probably the cause of the "NOT FOUND" error as the API couldn't recognize the account profile who is trying to access the report.

Regards,

Reply all
Reply to author
Forward
0 new messages