Stripe's 12-year API evolution from v1 to their major 2022 redesign

So, you know, most of the, the, you know, rest URI's that, people, are familiar with in Stripe are prefixed with slash v one.

28:01 / 28:43

had contemplated the possibility of this early at Stripe. So, you know, most of the, the, you know, rest URI's that, people, are familiar with in Stripe are prefixed with slash v one. They've been prefixed with slash v one from, you know, 2010. And, and so then in 2022, we decided, okay, we might use the, the, you know, increment the, the namespace. So we designed those new APIs. They started to ship, this year.

And Congratulations.

Thank you. And we're extremely excited about the functionality that it's going to enable. And, you know, without getting into the arcana of it, you know, they will enable things like historically, we have, we have drawn

About this clip

Patrick Collison explains how Stripe has been planning for API evolution since 2010, prefixing all REST URIs with '/v1' from the beginning. He discusses their decision in 2022 to finally increment their API namespace and ship new functionality that enables capabilities beyond their original architecture.

Why this clip

Shows exceptional long-term technical planning and the strategic thinking behind API versioning at one of the most developer-focused companies.

28:01 - 28:4341stactical advice

Share

LinkedInX

More from this guest

Patrick Collison

1 appearance · 6 clips

What they said next

Stripe realized their core APIs were fundamentally wrong and had to rebuild

27:29 - 45s · founder story

More from this episode

Similar clips from other shows

From the blog

Want clips like this for your podcast?

We find your top 5-8 clips, write the hooks, and deliver ready-to-post content. First 2 episodes are free.

Get 2 Episodes Clipped Free