<i>If Dropbox&#x27;s API was RESTful would that save me any time using Google&#x27;s competing API?</i><p>If Dropbox&#x27;s API was RESTful, you&#x27;d be able to use Google by only switching the initial URL - which could even be configurable by the user, or auto-discovered from the website.<p><i>When you start playing with the APIs from lots of different cloud storage folks (Dropbox, OneDrive, Google Drive) you see that they vary widely in concepts and capabilities.</i><p>They don&#x27;t vary _widely_ in concepts and capabilities, they add a layer on top of the same concepts (files, directories, upload&#x2F;download, get public URL), and REST allows you to support generic and specific clients easily, by either using extensible or multiple media types.<p><i>Also Dropbox&#x27;s old API was REST and it doesn&#x27;t seem more portable</i><p>It resembled REST, but it wasn&#x27;t. A good way to tell: if you need a documentation page with a list of all the URLs you can call, it&#x27;s probably not RESTful.