CM360 dynamicFeeds.insert fails with 400 error on RESOURCE_TYPE_REMOTE_FILE

[Sruthy M L]

We are attempting to create a Dynamic Feed using the dynamicFeeds.insert method (v5 API) by pointing to a valid, publicly accessible remote CSV file. The API consistently returns a 400 Invalid Argument error on the resourceType field.

Steps Taken & Error Details

1. API Method & Version: POST /dfareporting/v5/studio/dynamicFeeds

2. Failing Field Configuration: We used the following contentSource configuration:

   JSON

   "contentSource": { "resourceType": "RESOURCE_TYPE_REMOTE_FILE", "resourceLink": "" }

3. Resulting Error:

   JSON

   { "code": 400, "message": "Unsupported resource type: RESOURCE_TYPE_REMOTE_FILE", "errors": [ {"message": "Unsupported resource type: RESOURCE_TYPE_REMOTE_FILE", ...} ], "status": "INVALID_ARGUMENT" }

Contradictory Observation (Key Point)

The same remote file URL is successfully processed when creating a new Content Source via the Studio UI (Dynamic Content > Create new content > Select source: Remote file). This suggests the functionality works, but the API is rejecting the enum string.

Question for Support

1. What is the correct, supported string for resourceType when pointing to a non-Google-hosted CSV/XML feed URL using the dynamicFeeds.insert method in the v5 API?

2. Should we be using RESOURCE_TYPE_GOOGLE_SPREADSHEET even for non-Google links, or is this behavior a known API bug?

[DCM API (DoubleClick Campaign Mgr)]

Hi,

 

Thank you for reaching out to the DCM API support team.

I see that you are encountering a 400 error with the message "Unsupported resource type: RESOURCE_TYPE_REMOTE_FILE."

To help us investigate this issue further, please provide us with the complete JSON request body and response. I could see that some mandatory fields, such as dynamicProfileId and dynamicFeed, may be missing from the JSON you previously shared.

 

You can send the details via Reply privately to the author option, or direct private reply to this email. 

 

Thanks,
 

DCM API Team

Feedback
How was our support today?

               
[2025-11-03 16:52:36Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSUdn:ref" (ADR-00338316)