API connector and OAuth

[brentsum]

Agreed. While Blockspring and Zapier allow you to pull public data by connecting through a single social account, we need a way to access a user’s data via an API. Since doing any sort of authentication requires us to register an app with the API, the risk of abuse would be lower than public calls I’d imagine.

and @NigelG the Google Calendar example is a great one. A user should be able to create a calendar event in Bubble and then our app would send the event via Connector to Google’s API.

Looping in another relevant post:

API Connector - use most JSON APIs directly from Bubble

This depends on the token expiration. If the token is valid for say minutes or an hour, you can include it as a client-safe header for the second call. If the token nevee expires obtain it and then manually save it as a private header parameter on the call. We’ll enable native OAuth support soon, it looks like it’s needed. This will make the process transparent and secure, since it will be handled by our server.