Sheety 2.0 - Turn your Google Sheet into a fully RESTful API

Hello Product Hunt! Earlier this year I launched Sheety V1 which let you do basic reads from your Google Sheet via a JSON API. Since then over 800,000 people have used Sheety, and we serve nearly 80GB of sheets per month – you guys love spreadsheets! Today I'm launching Sheety V2 which now lets you write to your sheet. You can use standard RESTful interactions: GET, POST, PUT and DELETE. It's also blazing fast: updates happen in realtime. Getting up and running is as simple as connecting your Google account to Sheety, then pasting the spreadsheet URL: schemas and endpoints are generated automatically. I built Sheety V2 as I spend a lot of my timing prototyping new ideas, and wanted a quicker way of putting together realistic experiences that can be used in the wild! I can't wait to see what you do with Sheety and would love your feedback :-) Cheers

Scary to have a dependency with another direct dependency which could turn off access anytime. However definitively cool and interesting. For prototyping and more I’d definitively say it’s worth a shot

This looks super awesome and useful! Super clean and well explained landing page... Well done Phillip! :)

I really like the idea, but i don't like the pricing model. You should really concider expanding the free plan 500 requests per month is nothing.

Sheety v1 was super useful, so Sheety V2 sounds like a great upgrade. This is how Google Sheets public API should be. Great job @phillipcaudell

looks super cool, however was just curios does google drive exposes api for reading and specially writing purposes.

As a developer, I would love to have the capacity to consume the api as grapqhl. It would be really helpful to have typed queries, known which fields are being consumed (Benefits that with RESTful actually you can't). Good luck!

800K users!? That's insane man! Happy user here 👋 Looking forward to using Sheety for my next project.

Once you expose your endpoint in client-side JS, anyone could come along and wipe out your data by iterating through record/row IDs? Or write anything they want in there. So this is merely intended for prototyping, or there's another way to protect the data?

Incredible. I have followed this project for a long time. Amazed to see how much more work you have done on it. This is like the airtable of apis. Love it.