Blobr - Don't share APIs, offer API experiences

The API experience concept

APIs are no longer about data attributes. They are about the experience of users. Users are looking for a valuable, quick, tailored, consistent, transparent, and predictive process that solves an API related pain point.

Valuable

Users want APIs that have a specific use case focused on solving an issue.

Quick

As time is money, users want to test quickly. Time to first call is critical.

Tailored

Customers want an API that meets their exact needs.

Consistent

From exploration to onboarding, the API experience should be consistent.

Predictive

Each action and outcome of the APIs and API portal should be user-centric.

Transparent

All info should be available at the users' fingertips. Transparency leads to trust.

Common challenges with an API experience

APIs are everywhere but consuming them is still difficult. The reason is simple. It's a long & painful process to expose APIs in a way that is easy for customers to use them.

Engineering teams

Engineers are frustrated by the amount of time they spend on API sharing, documentation and management. They want to focus on building new features that create value.

API users

API users are fed up with long docs. The API experience is inconsistent and unpredictable. They don’t want to buy APIs or attributes; they want to solve issues.

Product teams

Product teams often lack the technical support they need from engineering teams. They want to create a high-quality API experience that optimizes adoption but don’t have the coding skills required.