giuliano84
Building an AI-powered digital asset manager with Box and Clarifai
Prospector: find key contacts at a company from Slack using Clearbit
Re:Webhooks do’s and dont’s: what we learned after integrating APIs
on Tuesday November 22, 2016 @01:21PM (#13016166)
Point 3 is spot on. I think it would be a good strategy to avoid expire dates on subscriptions. Producers could take decisions on whether or not keep sending data by monitoring responses on the consumer's target URL.
Another thing that it should be worth mentioning is that some services batch notifications (e.g Facebook Messenger) so that they can send more data in a single POST request.
Re:Webhooks do’s and dont’s: what we learned after integrating APIs
on Tuesday November 22, 2016 @01:19PM (#13016141)
Yes but that's why you build webhook for, to let people consume your content. I think DX is critical today and big companies can afford to do the heavy-lifting. As I mentioned in the Subscription Expiration paragraph I totally get Microsoft's reason to put a 72hrs expire date on subscriptions but it adds some friction on the consumer side.
Re:Webhooks do’s and dont’s: what we learned after integrating APIs
on Tuesday November 22, 2016 @01:17PM (#13016125)
True. Also having a sample request at the very beginning is useful so you don't have to find a way to trigger the event by clicking around on the product UI.
Re:Webhooks do’s and dont’s: what we learned after integrating APIs
on Tuesday November 22, 2016 @01:16PM (#13016109)
Agreed. I believe that AMQP connections are best suited for wide and articulated local environments. Moreover REST HTTP endpoints are today's esperanto :)
Webhooks do’s and dont’s: what we learned after integrating APIs
Build a translator Slack slash command with IBM Watson
Using IBM Watson to detect Facebook messages tone and prioritize support
Getting started with your first Kik bot
Re:Apply HN: Brightwork – Making APIs More Intelligent
on Thursday April 07, 2016 @12:00PM (#11448312)
Hey guys, Stamplay's founder here!
It's hard to say by a simple landing page but the service looks quite different in terms of offering.
The visual workflow builder of Stamplay is just a fraction of the whole offering and can be used by developers to orchestrate services or build business logic of their apps quicker.
Aside from that we to offer out of the box User authentication and management API, social signup, Data storage API with automatic generation database and REST API on top of the data model you define, Serverless code execution to implement any custom logic (AWS Lambda like), 3rd party API integrations (Stripe, Sendgrid, Twilio, Firebase, AWS SNS, AWS SQS.. and more), Cronjobs, Webhooks, CDN backed hosting for static assets with SSL + custom domain support.
As long as you understand basic RESTful services, JSON and JavaScript you can use all our core API. Modularity is a key factor of our platform and developers can already share "Code Blocks" to add specific features to their apps.
Brightworks seems more close to be an API design tool and to manage it over the time but I look forward to see more :)
Show HN: How to create cross-platform apps with Ionic and Stamplay
Building SMS Weather Forecasts with Twilio and Node.js
Build a Weather by SMS Service with Twilio and Node.js
Pipe in fully enriched user profiles on Slack with Clearbit and Stamplay
The age of bots and back end as a service
Why you shouldn’t be upset if you built with Parse
Getting started with Angular 2
Getting Started with React ES6 and Webpack
Discover the anonymity level of your email address
Building a Hacker News Clone Without Writing any Back End Code
Re:HTTP Status Cats API
on Wednesday September 02, 2015 @03:10PM (#10161330)
When developers meet cats...