This one has been awaited for a long time, and we’re happy to release it today. We’re calling it beta as we expect a few cases we don’t handle yet (each API comes with different situations).
You can now add your own APIs for authentication, provided they follow the standard OAuth2 protocol. This will let you
let your users authenticate with services we don’t have yet (let say, Spotify)
get data and post data to these services as the logged in user.
In short, it’ll be very much like what you can already with Facebook, Pinterest, etc.
You need to be familiar with these things a little bit to set it up, as you need to find the relevant endpoints and other info in the documentation of the service, but there is no code needed See below what it looks like for Spotify.
You’ll need to find the two URLs for authorization and to generate the server-side token request, and the endpoint to get the current user’s profile. What we need here (it’s necessary), is the ID of the user, let’s say in Spotifiy. If you have email access in the scope, you’ll get it from there, but it’s not necessary.
One important thing to note is that you need to test the flow as yourself, with the debugger being present, so that we have have a token to test the calls that you’ll add afterwards. And if for some reason the token expires, you’ll be prompted in the box to go to run mode, go through a workflow that signs you with Spotify to get a new token.
If you hit weird situations, error messages that don’t make sense to you, please file a bug report.
I got the Google Calendar API to work (developer console is saying no errors) and I got redirected back to my app, but I still don’t get the API being marked as valid. Interestingly I didn’t get anything back on the URL.
Yes, by design we always bring back users to where they’re from (same is you use facebook). it’s important if the workflow has more actions after this, which is usually the case.
We save the code, generate the token behind the scene, so you shouldn’t have anything in the URL.
Regarding Google and your app I get this below. Google is extra-super-annoyingly strict about URLs, so it may be about this.
Please send us a bug report if the API isn’t marked as valid after you successfully sign up.
In terms of the page redirect… how can you tell the the user has authenticated ? So how can I change the page based upon having authenticated. So I have a button “connect your account” … and I don’t want to come back to the same button. You tend to have an oauth2redirect page.
Well you can put this at the next action in the workflow, go to another page, etc. This is exactly as facebook works (the API connector doesn’t make anything different).
This is great news, Emmanuel, we’ve been waiting for it One question, i wanted to connect Google Adwords API for our client and it says that it’s a SOAP one. Can it be used with Bubble?
We already support this actually (if you see the App section in the API tab of the settings tab. If that’s of interest we can talk about it by email, at this stage we haven’t worked much on documentation for this yet.
That’s right Google Adwords says that it’s SOAP XML API, i didn’t try yet because i wanted to know first if it’s supported… Do you think it’s worth trying or you are certain that it won’t work?
This is awesome! For existing plugins like Facebook + Twitter, is there a way to get the Oauth access tokens from the existing authentication flow and use them? Or should we build separate flows using the new connector?