arnihermann

I'm a developer at GRID [1]. GRID turns spreadsheets into interactive web documents, and we recently built a system which allows our users to effectively turn their spreadsheets into a web service and query it via a JSON API.

I recently tweeted [2], asking if some of my friends had ever re-implemented spreadsheet logic in code or otherwise wished they could've accessed spreadsheet values through an API. A few reached out and now I want to get a broader look at the problem we're solving.

To clarify what I mean by turning a spreadsheet into an API, let's take for example this Dog age calculator [3]. There's an underlying spreadsheet behind this web page with all the formulas for the calculator. Here's an example of how we can use our API to find out the dog age of a large 8 year old dog:

  $ curl 'https://thesystem.grid.is/@grid_examples/dog-age-calculator-Yjk:Fsm0Rj2mtJVcKqzr7g' -d '{
    "read": [ "J3" ],
    "override": {
      "G3": 8
    }
  }'

  {
    "data": {
      "J3": {"value": 55}
    }
  }

The API is not live yet – this is just an example but it shows the request and the response. The request is doing a few things: changing the value of cell G3 (the age input cell) to 8, and then reading cell J3 which is the computed dog age for large dogs. The underlying Excel file is downloadable if anyone wants to look at it [3].

So my ask is this: Does HN relate? Do you ever wish you were able to turn a spreadsheet into an API instead of re-implementing it in code – and then query it from your server (or JS in browser)? Does the API make sense to you and do you think it would be useful? If not, how could we improve it?

Would love to hear your thoughts. Also, let me know if you’d like to try it out – we’re looking for a few users to give us feedback on the API itself.

[1]: https://grid.is

[2]: https://twitter.com/arnihermann/status/1425116225986834435

[3]: https://grid.is/@grid_examples/dog-age-calculator-Yjk:Fsm0Rj2mtJVcKqzr7g