Welcome to API Design Matters.


Welcome to API Design Matters.

In this substack, I explore API Design and Developer Experience matters large and small, topics around building and running API programs... that is, why API Design Matters.

I’ll focus on RESTful web services, but many of the concepts apply to other API styles like AsyncIO, GRPC, and GraphQL. Articles will pull from my 12 years experience designing RESTful APIs using OpenAPI, but include echos of designing traditional programming language interfaces and libraries over 30+ years of my career.

API Design is truly an art, and while ChatGPT can spit out basic APIs, there is still much to be said for well-crafted consistent APIs designed in a broader context, with the consumer and Developer Experience in mind.

A good (or great) Developer Experience (DX) is an important aspect of API design, and this substack will often discuss the interplay of API design and DX: how and why API Design matters to DX.

Intro

I’m David Biesack. I am Chief API Officer at Apiture. Apiture is a Software-as-as-Service provider of digital banking to hundreds of financial institutions across the US. There, I am responsible for API architecture and design and Apiture’s Developer Experience and Developer Portal.

Prior to joining Apiture in 2017, I worked at SAS in Cary NC for 28 years. For my last 5+ years at SAS, I ran the API Center of Excellence which managed SAS’ API standards and API review process , assisted teams with API design, and otherwise helped with SAS’ adoption of REST APIs. In my earlier positions at SAS, I designed and built a list library and object programming system for the SAS Command Language, was R&D Java Strategist as SAS adopted the Java platform starting in 1996, designed and implemented boatloads of Java APIs, did a stint in the Advanced Computing lab researching highly parallel multi-dimensional data servers and distributed programming languages, and built a few Scala libraries.

I will begin the API Design Matters substack with an extensive series on The Language of API Design. This five part series will focus on the API First process to complete learning projects with the OpenAPI 3 Specification—why API Design with OpenAPI matters.

Outro

Enough about me. I hope to hear from you - what topics of API Design are top of mind? How do you approach the design process? Let’s have a conversation.

You can also find me on mastodon.social/@DavidBiesack (no ɹǝʇʇᴉʍʇ, thank you).

Subscribe now

Unsubscribe

David Biesack

David Biesack serves as Chief API Officer at Apiture. David applies his passion for building great APIs and a compelling developer experience to the design and architecture of Apiture's Amazing API ecosystem. David has over thirty years of industry experience creating reusable, robust, and elegant enterprise software systems. He strives to make software [development|developers] better, stronger, faster at solving complex customer problems.

Read more from David Biesack
"Behind the API" featuring David Biesack

The Reality of API Programs Shane O'Conner (Founding Team @ Scalar ) has started a new Q&A series on LinkedIn called Behind The API. Shane graciously asked me to participate, and also allowed me to re-publish the content here. Below is Shane's initial announcement of the Q&A, followed by the full content. Introduction Below is Shane's first LinkedIn announcement on Nov 11, 2025, sharing the "Behind The API featuring Davod Biesack" article: Shane wrote: I've been thinking a lot about what...

No Robustness for you

Note: Below is an article I originally wrote for Nordic APIs, published as Meet Hyrum and Postel on December 9, 2020. -- djb, Nov 16, 2025 How do Hyrum’s Law and Postel’s Law affect API designs? Luckily for us humans, and especially that narrow subclass of humans who build APIs, API design is a field that has not been automated or botified… yet. Sure, one can point at a database schema and generate what one can label an “Application Programming Interface.” But it is an API only in a literal...

Thumbnail - API Design First is not API Design First

To kick off The Language of API Design series, we will take a brief but important diversion from the OpenAPI Specification and it’s unique but powerful language of API design. Our detour will focus on a different sort of language: the ubiquitous language. In other words, today, I’m “Mr. Language Person”.1 The term “API Design First” is quite popular now, but it is misleading. If one began by first creating an API design (fun as that may be for some of us), the result is likely not going to...