DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Secrets in Code: Understanding Secret Detection and Its Blind Spots
  • Automating FastAPI Deployments With a GitHub Actions Pipeline
  • Building Secure Transaction APIs for Modern Fintech Systems Using GitHub Copilot
  • Vibe Coding With GitHub Copilot: Optimizing API Performance in Fintech Microservices

Trending

  • Stop Writing Database Migration Scripts: Declarative Schema Sync for Java
  • How to Migrate From C/C++ to Rust: A Practical Guide for Embedded IoT Systems
  • Build a GitHub Contribution City With Java and Quarkus
  • Searching Kafka Without an Index: Lessons From Building Message Search for Kafdrop

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

  1. DZone
  2. Data Engineering
  3. Databases
  4. Stripe's OpenAPI Is Available on GitHub in Version 3.0

Stripe's OpenAPI Is Available on GitHub in Version 3.0

The payment provider Stripe is a great example of a leading API provider publishing their OpenAPI to GitHub and embracing OpenAPI version 3.0.

By 
Kin Lane
·
Nov. 17, 17 · Opinion
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
8.1K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

I can’t write about every API provider who publishes their OpenAPI to Github, there are just too many. But, I can write about the rockstar API providers who do, though, and showcase what they are doing, so I can help influence the API providers who have not started publishing their OpenAPIs in this way. If you are looking for a solid example of a leading API provider publishing their OpenAPI to Github, I recommend taking a look at the payment provider Stripe.

Their repository contains OpenAPI specifications for Stripe’s API, with multiple files available in the in the openapi/ directory:

  • spec3.{json,yaml} - OpenAPI 3.0 spec.
  • spec2.{json,yaml} - OpenAPI 2.0 spec. We’re continuing to generate this for now, but it will be deprecated in favor of spec3.
  • fixtures3.{json,yaml} - Test fixtures for resources in spec3. See below for more information.
  • fixtures2.{json,yaml} - Test fixtures for resources in spec2.

It is pretty exciting to see them already embracing version 3.0. They even provide a listing of the OpenAPI vendor extensions they are using, which are specific to their API. I’ll be adding these to my OpenAPI toolbox when I have the time, adding to the number of vendor extensions I have indexed. Stripe provides another pretty solid example of an API provider taking ownership of their OpenAPI spec, publishing to Github for their consumers to put tow rok, but clearly, they are also using as part of their own internal workflows as well.

Every API provider should have a Github repository with an up to date OpenAPI like Stripe does. I know many API architects envision a hypermedia API discovery landscape, where APIs are defined and discoverable by default, but I think an OpenAPI on Github is the best we can hope for at this stage in the evolution of the space. With the momentum I’m seeing in the number API providers publishing their OpenAPIs to Github, I’m feeling like Github is going to become the continuous integration, API discovery engine we’ve all been looking for over the last decade. Allowing us to discover, integrate and orchestrate with our APIs across the API life cycle–we just need everyone to follow Stripe’s lead.

GitHub API

Published at DZone with permission of Kin Lane. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Secrets in Code: Understanding Secret Detection and Its Blind Spots
  • Automating FastAPI Deployments With a GitHub Actions Pipeline
  • Building Secure Transaction APIs for Modern Fintech Systems Using GitHub Copilot
  • Vibe Coding With GitHub Copilot: Optimizing API Performance in Fintech Microservices

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook