Examining Mature APIs (Slack, Stripe, Box)
Where is API development headed? See how these three companies have chosen to focus the functionality of their mature APIs with webhook events.
Join the DZone community and get the full member experience.Join For Free
in our previous blog post , we discussed the disconnect between api pricing plans where you pay monthly for a set number of calls and regular developer use cases. we think competition will drive new pricing models that are more developer friendly – and a potential approach could be charging for calls based on their business value. examining webhook events available via api from stripe, slack, and box gives us a forward look into how this could work.
what’s a mature api?
forbes nicely summarizes where they see api development going in this graphic (ignore the “customer-driven platform revolution”) portion:
they make a valid point that apis become more valuable as the data that flows from them becomes bi-directional – apis are not only returning data based on calls, but actively pushing out data based on api activity.
this data push generally starts around activity with high business value – so we’re going to examine apis from stripe, slack, and box to get an idea of what events they make available.
slack has a separate “events api”
slack has chosen to implement a separate events api for developers who want to build apps that respond to events within slack. here’s the full list of event types that they can push in real-time as they happen.
looking at this list in more detail, it’s focused on key messaging and collaboration activities:
- creating and updating channels
- uploading, sharing, and commenting on files
- messages being posted to various channels
box uses event triggers
box uses webhooks with event triggers attached to box files and folders to monitor events attached to files and folders and notify you when they occur. here’s their full list of events for files and folders.
as expected for box, events are focused on file management and collaboration:
- uploading, previewing, and downloading files
- comment and task assignment creation and updating
stripe sends a variety of events
stripe sends a wide variety of events around payments, both keyed to internal and external usage:
- account creation and updating
- product or plan creation
- card charges and updates
what does it mean?
the events that these mature apis have chosen to make available for realtime push have substantial business value for developers building apps using their functionality. as more apis begin to offer push of data, they may move to a blended pricing model that charges more for these high-value events. we’re interested to see what happens!
this post originally appeared on the fanout blog .
Published at DZone with permission of Daniel Kadvany, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.