21–30 of 103 posts
1. How to get columns? 2. Your docs say: http://sheetsu.com/apis/12345/column/:column_name Is ':' a documentation convention somewhere that I've not come across? I tried: http://sheetsu.com/apis/12345/column/:Email http://sheetsu.com/apis/12345/column/:email until I realised it was just: http://sheetsu.com/apis/12345/column/Email
That's nice - I've recently made a small project to wrap Github's Gists around an open API[1] for the same use case - a small open database easily browseable -, but your project seems much more interesting - spreadsheets are a very interesting way to solve this. Good job. [1] https://github.com/arcanis/gist-proxy-server
Cool. Is there any API rate limit?
Cool. Is there any API rate limit?
Right now, it's Google Drive Quota. I'm testing out the idea, etc. If it goes well I'll probably cut rate limits per user or per API.
Anyways, it's really handy for simple and non traffic-intensive projects. Well done!
If you were to extend the functionality to include full CRUD on entities, I think I would start using it immediately on some proof of concept work.
For instance, being able to GET, PUT/PATCH, and DELETE by id (or per row) would be awesome.
Thanks again for the nice MVP work!
Google Spreadsheets is awesome as a quick and dirty CMS. I use it all the time at the newspaper i work for, in combination with Tabletop ( https://github.com/jsoma/tabletop ). Only thing i lack right now is some kind of library that could cache those sheets using Redis for speed.
Ah man, this is perfect! finally a way to get simple servers running with very little hassle. One major feature I would like is the ability to specify cells for I/O. Eg in some sort of "my api" console I could say "/custom_api, {stuff:A5, things:A6}, B2". Then requests to GET /custom_api would plug in the key-value of "stuff" into A5 and "things" into A6 and then respond with whatever is in B2. Once more useful featu…