3 ms·

I don't think so. I just need to procure an API key and some credentials from Cloud Console to begin using Sheet API. The rest is just a lot more backend develo

I don't think so. I just need to procure an API key and some credentials from Cloud Console to begin using Sheet API. The rest is just a lot more backend development for me.

hogFeast 6y ago
Right, but won't you need permissions to access data in user accounts? You can only get permissions with a Google audit (which you have to pay for).
- thesandlord 6y ago
  No, the easiest way is to use a service account and share the sheet with the service account. No need for user OAuth at all. https://github.com/juampynr/google-spreadsheet-reader https://github.com/juampynr/google-spreadsheet-reader
  - hogFeast 6y ago
    Would you build a livelihood on that? I have heard of that but it sounds like the kind of loophole that got the industry into a situation where you needed to pay tens of thousands to use an API.
    - thesandlord 6y ago
      > Would you build a livelihood on that? Yes? Google is notorious for deprecating and changing things, so I would have a backup plan but companies like Streak have built large businesses on much more restricted APIs like Gmail. > kind of loophole This is not a loophole, this is 2-legged Oauth. This is much safer than the typical 3-legged Oauth where the user gives blanket permission to read and write from their Google Drive. The user has to explicitly share the sheet with this service account email. Google is trying to protect people from clicking a phishing link and getting all their email and drive content stolen or hijacked. Yes, Google can shut this down tomorrow or demand thousands of dollars to use it. It's a inherent risk building on top of someone's platform, the trade off being you get the scaffolding and user base the platform already has.
- detaro 6y ago
  You might be mixing up access to GMail APIs with general access to Google APIs? Reading people's emails comes with tons of red tape, other things not so much.
  - hogFeast 6y ago
    I am not - https://support.google.com/cloud/answer/9110914?hl=en https://support.google.com/cloud/answer/9110914?hl=en - after Facebook, everyone is tightening up these permissions.
    - deleted 6y ago
      [deleted]
    - detaro 6y ago
      Okay, it's wider than just GMail, I had missed the addition of Drive, but according to that link an audit is just required for > Drive - Any Drive API scope that permits an application to read, modify, or manage the content or metadata of a user’s Drive files, without the user individually granting file-by-file access. I could be wrong, but to me this suggests you can use the Sheets API against a user-specified document without it. It has it's own namespace of scopes that's not under drive.X
      - hogFeast 6y ago
        Correct, an audit that can cost somewhere between $10-70k (you pay, not Google)...like I said in my first post.
        detaro 6y ago
        Yes, sure. But again, according to the link you provided, you do not need that audit to use the Sheets API.

I don't think so. I just need to procure an API key and some credentials from Cloud Console to begin using Sheet API. The rest is just a lot more backend development for me.

hogFeast 6y ago

Right, but won't you need permissions to access data in user accounts? You can only get permissions with a Google audit (which you have to pay for).

thesandlord 6y ago
No, the easiest way is to use a service account and share the sheet with the service account. No need for user OAuth at all. https://github.com/juampynr/google-spreadsheet-reader https://github.com/juampynr/google-spreadsheet-reader
- hogFeast 6y ago
  Would you build a livelihood on that? I have heard of that but it sounds like the kind of loophole that got the industry into a situation where you needed to pay tens of thousands to use an API.
  - thesandlord 6y ago
    > Would you build a livelihood on that? Yes? Google is notorious for deprecating and changing things, so I would have a backup plan but companies like Streak have built large businesses on much more restricted APIs like Gmail. > kind of loophole This is not a loophole, this is 2-legged Oauth. This is much safer than the typical 3-legged Oauth where the user gives blanket permission to read and write from their Google Drive. The user has to explicitly share the sheet with this service account email. Google is trying to protect people from clicking a phishing link and getting all their email and drive content stolen or hijacked. Yes, Google can shut this down tomorrow or demand thousands of dollars to use it. It's a inherent risk building on top of someone's platform, the trade off being you get the scaffolding and user base the platform already has.
detaro 6y ago
You might be mixing up access to GMail APIs with general access to Google APIs? Reading people's emails comes with tons of red tape, other things not so much.
- hogFeast 6y ago
  I am not - https://support.google.com/cloud/answer/9110914?hl=en https://support.google.com/cloud/answer/9110914?hl=en - after Facebook, everyone is tightening up these permissions.
  - deleted 6y ago
    [deleted]
  - detaro 6y ago
    Okay, it's wider than just GMail, I had missed the addition of Drive, but according to that link an audit is just required for > Drive - Any Drive API scope that permits an application to read, modify, or manage the content or metadata of a user’s Drive files, without the user individually granting file-by-file access. I could be wrong, but to me this suggests you can use the Sheets API against a user-specified document without it. It has it's own namespace of scopes that's not under drive.X
    - hogFeast 6y ago
      Correct, an audit that can cost somewhere between $10-70k (you pay, not Google)...like I said in my first post.
      - detaro 6y ago
        Yes, sure. But again, according to the link you provided, you do not need that audit to use the Sheets API.