This is an example of how to use the Google Drive file picker and Google Drive API to retrieve files from Google Drive using pure JavaScript. At the time of writing (14th July 2013), Google have good examples for using these two APIs separately, but no documentation on using them together.
Note that this is just sample code, designed to be concise to demonstrate the API. In a production environment, you should include more error handling.
See a demo at http://stuff.dan.cx/js/filepicker/google/
- Get a Google Drive API key (refer to Google's Quickstart guide for instructions).
- Replace
PUT_YOUR_API_KEY_HERE
with your API key (listed under "Key for browser apps" in Google's API console) - Replace
PUT_YOUR_NUMERIC_CLIENT_ID_HERE
with the numeric portion of your OAuth2 client ID (xxxxxxxxxx.apps.googleusercontent.com) - Test out the code to ensure it works
- Replcae the onSelect method with your own code
- Google Picker API Developer's Guide
- Google Drive SDK - API Reference
- JavaScript Client Library Reference
(The MIT licence)
Copyright (C) 2013 Daniel Lo Nigro (Daniel15)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
A bit of a shot in the dark, but hoping someone with experience here can help clarify the true function of the picker API for me & my team. We were able to successfully implement the Picker API, but its true function seems to be just a UX to more easily pick files.
Our app is seeking to oAuth into a user's file (specifically GSheet), where we'll upload data each day on a schedule. The Google Verification team suggested the Picker API and drive.file scope in order to do so, but we're unable to successfully gain permissions to the file in question, to actually edit the contents of the file (by writing data to one of the tabs, and/or creating new tabs in the Gsheet).
If anyone has advice on how to leverage the drive.file scope and Picker API to gain access to a file, and update/edit that file, it would be a massive help. Otherwise, if that's truly not the function of this scope, it would be equally valuable to know that definitively. Thank you, in advance!