Using save_url w/out specifying folder name

The equivalent of API v1's /1/save_url in API v2 is /2/files/save_url. 

Both of those endpoints do require that the app specify the destination path for the file, in the "path" parameter.

The "auto" value from v1 was used in the "root" parameter, which identified the access type of your app ("sandbox" or "dropbox"), or let the API detect it for you ("auto"). The root parameter is not necessary for API v2, which will always use the "auto" behavior for you.

So, when using API v2's /save_url, if you just supply the filename and extension, e.g. "/filename.ext", it will be placed in the app's root, either full Dropbox or an app folder depending on the permission, like it would in API v1 when you specified "auto".

If the endpoint isn't working as expected of course, please share some code and output showing whatever issue you're running in to and we'll be happy to help.

Thank you Gregory. I am having some issues in regards to where the API is reading and writing to when I leave out the folder name.

For example,  I have an app whose App Name is My App. The access type says "This app has read/write access only to files inside it's folder".
If I use save_url (https://api.dropboxapi.com/2/files/save_url )  and I only specify the file name (for example myfile.txt), the file gets written to Dropbox and not Dropbox->Apps->My App.

A related issue is as follows: If I do specify the folder name in save_url (/My App/myfile.txt), the file is saved to that folder (Dropbox->Apps->My App).
However, when I specify /MyFolder/myfile.txt when running get_metadata, I get a Httpstatuscode of 409. If I only request /myfile.txt (excluding the foldername), get_metadata will find the file.  Please help me understand how I should be able to write a file and check for that file.  

Larry

Thanks for the additional information Larry. We're looking into it and I'll follow up here once I have an update for you.

Hi Larry, this should be working as expected again. Please let me know if you're still seeing any issues.

Yes, works as exptected now.  Thank you much.