I profiled Stripe and Twilio using APIs.json recently. My API profiling process requires that I get to know an API, and while Stripe and Twilio do not maintain their own APIs.json index, they both do maintain OpenAPI for their APIs-—they just do it differently from each other. Stripe chooses to use one large OpenAPI for every path and operation they provide. Twilio chose somewhere along the way to break theirs down into modular OpenAPIs. I worked with both of these companies while working at Twilio, so I have insight into the pipelines behind the generation of these OpenAPI. While I am glad both companies maintain their own OpenAPI, in my experience it just makes more sense in the long run to break your OpenAPI into modular parts, which go a long ways to reducing the cognitive as well as the processing load involved with putting each API to work.

API Evangelist's publication is a resource for developers, architects, and technology leaders seeking to understand the importance of APIs in modern software development. Through articles, case studies, and industry insights, API Evangelist offers insights into API design best practices, API management strategies, and API-driven business models. Readers can learn about RESTful API principles, GraphQL implementations, and microservices architecture to build scalable and interoperable software systems.

API Evangelist

Comparing Stripe and Twilio's approach to OpenAPI, Twilio chooses to break their OpenAPI into modular parts while Stripe prefers to keep theirs as a single file.

Stripes Monolithic OpenAPI vs. Twilio Modular OpenAPIs