Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

A Missed Opportunity with the Medium API

DZone's Guide to

A Missed Opportunity with the Medium API

I get that control over the user experience is key to the Medium model, but there are examples of how this can be done well while still having an API.

· Integration Zone
Free Resource

Learn how API management supports better integration in Achieving Enterprise Agility with Microservices and API Management, brought to you in partnership with 3scale

In addition to using the news of Medium's downsizing as a moment to stop and think about who owns our bits, I wanted to point out what a missed opportunity the Medium API is. Having an API is no guarantee of success, and after $132 million in three rounds from 21 investors, I'm not sure an API can even help ou. However, it is fun to speculate about what might be possible if Medium had robust API in operation.

Medium has an API, but it is just a GitHub repository with reference to a handful of paths allowing you to get details on yourself, the publications you are part of, and post entries to the site. There are no APIs for allowing me to get the posts of other users or publications, let alone any of the analytics or traffic for this. I'm guessing there is no API vision or champion at Medium, which results in the simple, restrictive API we see today.

Many media and content companies see APIs as giving away all the value they are trying to monetize and are unaware of the control that modern approaches to API management bring to the table. Many people see the pain that other API pioneers have suffered like Twitter and want to avoid the same problems, completely unaware that many of Twitter's ecosystem problems were Twitter-induced and not inflicted by third-party developer.

If Medium had a proper developer portal, complete set of API paths, proper OAuth controls, and other API management tooling, they could open up innovation in content delivery, publishing, analytics, visualizations, voice, bot, and the numerous of other areas where APIs are changing how we consume, create, and engage with information. I get that control over the user experience is key to the Medium model, but there are examples of how this can be done well while still having an API. The best part is it only costs you the operation of the API operations.

I do not think more money will save Medium. I think they have to innovate. I think part of this innovation needs to come from the passionate base of users they have already developed. I've seen Medium carefully plot out a path forward when it comes to their trusted partners, and there is no reason this type of quality control can't be replicated when it comes to API consumers as well as the applications and integrations that they develop. The Medium API just seems like a really huge missed opportunity to me, but of course, I'm a little biased.

Unleash the power of your APIs with future-proof API management - Create your account and start your free trial today, brought to you in partnership with 3scale.

Topics:
integration ,api ,medium

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}