API Product Design

API product design is the product discipline of treating an API, documentation, examples, and developer onboarding as the main user experience. In Patrick and John Collison on Stripe’s Origins, Developer Products, and Long-Term Ambition, Patrick Collison and John Collison describe Stripe as emerging before there was a complete playbook for API companies, even though Twilio and Heroku provided useful nearby examples.

The source makes documentation and ergonomics central rather than cosmetic. Stripe became known for being built for programmers because the product reduced the time between a software idea and working payment code. In this frame, an API is not merely a backend integration surface; it is a product surface with activation, trust, support, and distribution problems.

Key Claims

• API companies need product design around first use, examples, errors, documentation, and developer trust.
• Developer ergonomics can be strategic when customers are bottlenecked by their ability to turn ideas into working software.
• Infrastructure APIs sell a capability that may be invisible to end users but decisive for whether customer products can launch.
• Early API companies had to invent parts of their own distribution and product language because the category was not yet mature.

Connections

• Stripe, Patrick Collison, and John Collison - source case.
• Developer-First Payment Infrastructure - payment-specific version of the API-product pattern.
• Entrepreneurship Infrastructure - broader category of tools that lower startup setup barriers.
• Agent-Facing Interfaces and Headless Software - later wiki concepts where machine-facing or programmatic interfaces become central product surfaces.