Dropbox API usage with trailing slashes

[Project Luca]

Hey guys,

Our dropbox implementation appeared broken on production environment  and we saw that a trailing slash on the following endpoint returned a unknown API endpoint error. This seemed to work fine ( with the trailing slashes "/" ) until earlier this week and looks like a recent regression. Also, am not sure if its just this endpoint that returns this error with trailing "/" or other endpoints are affected by this as well. 

It would be great if you could notify the clients before making such a change? 

Doesnt Work:

curl -X POST https://api.dropboxapi.com/2/files/list_folder/ \

 --header 'Authorization: Bearer XXX' \

 --header 'Content-Type: application/json' \

 --data '{"path":""}'

Unknown API function: "files/list_folder/".%    

Works:

curl -X POST https://api.dropboxapi.com/2/files/list_folder \

 --header 'Authorization: Bearer XXX' \

 --header 'Content-Type: application/json' \

 --data '{"path":""}'

Thanks

-Vasanth

[Greg-DB]

Thanks for the report Vasanth, and apologies for the trouble! It looks like there was a recent change to our routing system that changed the handling for calls with an extra trailing slash like this.

We of course never intend to release breaking changes without notifying developers. The API v2 routes are documented without a trailing slash though, so this wasn't on our radar as something to notify developers of.

[Project Luca]

 Thank you for the confirmation Gregory. Do we know when exactly this change was effected? 

-Vasanth

[Greg-DB]

I believe the change rolled out on Monday, the 6th.