ooh an IFTTT channel API!Thanks @Dave that sounds godsent! where can I find instructions for it? did I miss it in the documentation?
Is there any updates regarding IFTTT channel API?
In two legged authentication, only customer’s email is registered on Particle & No password required, on behalf of my organization and our org get access_token of customer from Particle. If customers want to use Particle IFTTT channel, then how can they use, as they’re not registered directly on Particle and they’ve no password to sign in directly to Particle account?
We do have an IFTTT Api Api, happy to share notes on that. If you’re not using our customer / user authentication system, then you’ll need to perform authentication against your API, which means IFTTT will be pointed at you and not at us. You could setup a proxy API in this case, and let your server do the auth, and pass the device requests to us using your main access_token. Or you could create shadow customer accounts and use those accounts while hitting us for IFTTT requests.
Happy to share details on our IFTTT Api Api if you’re at that stage.
As I’ve implemented two legged authentication and now I’m ready to implement IFTTT Api Api. Please share the details.
Sure thing! I’ll dig up / write up the documentation. It’s only used by a few community members since getting an IFTTT Channel can be tough, so it might take me a day or so to find. Sorry about the delay!
No Problem @Dave, I can wait
It will be great thing for my customers if I implement this.
Thank you so much!
Its more than 1 month. Is there any update on this? I’m eagerly following this topic since Apr 5.
Sorry about the wait, I haven’t had a chance to work on this, we’ve been really busy preparing for Maker Faire. I’ll try not to keep you waiting much longer.
Okay Dave! I can understand. Thanks.
We’re also on two-legged auth, so I’d also love the API info.
However, I really doubt that we’ll get our own IFTTT channel anytime soon. So I was hoping that in the interim we could post IFTTT recipes that use Particle’s channel. The issue is that a customer can only subscribe to the Particle Channel with username/password credentials. If you allowed a token-only subscription to the Particle Channel we could make things work. i.e.
- Our Customer learns they can use IFTTT recipes with their Particle powered product.
- We generate a never-expiring Particle token, scoped to this Customer from our server.
- Customer subscribes to the Particle channel using this token.
- Customer adds our recipe to their account.
- If ever customer feels the token has been compromised, or want to leave IFTTT, they simply request we delete the token.
This means the Customer couldn’t do this if they also wanted to use their own Particle account… but in our case there is really no overlap in client demographics. So I can’t imagine it being an issue.
Hmm, so in this scenario we’d extend the oauth login window to allow providing an access_token directly? If you’re generating a token for them, would it be a stretch to provide them customer username/password credentials to login to IFTTT with?
Can I do that with two legged Auth? We’re creating Customers with no password… I suppose we could create them with a password?
That would allow you to be up and running quickly, otherwise it’ll probably take us at least a few sprints before we could make that option available on the oauth login page.
Sorry I don’t have any updates on this yet. I handed that project off to @bryce, lets ping him and give him some time to respond, I know they’re pretty busy today.
Actually, I want to give IFTTT function to my customers next month.
It is the screenshot of my product dashboard screen. Only IFTTT integration is missing.
Good question! Sorry about the delay on that, I passed your message onto the team and hopefully they’ll respond here sometime early next week.
The two ways a powered product could use IFTTT right now are:
- Use 3-legged, “Login with Particle” OAuth to allow the end customer to set up IFTTT using the Particle channel, or
- As a product creator you get your own IFTTT channel and use 2-legged auth with Particle white-labeled behind the scenes.
The feature @dave was talking about is not released or documented yet. We don’t want to circumvent IFTTT’s business model as they’re a valued partner, but if we can provide a way to use your own IFTTT channel with Particle’s servers so you don’t have to deploy and maintain your own server for IFTTT, we think product creators would find that super exciting and valuable.
Thank you for prompt response.
Now, I can understand the scenario. I used two-legged authentication and for IFTTT channel, point 2 make sense for me. Perhaps, it would be great.