OpenAPI and Transparent Process
At LaunchDarkly, we’ve put a bunch of time into making our dashboard fast and usable, and we’re pretty proud of it.
However, we’re aware there are lots of reasons people would want to use an API to create and manage feature flags. Since we are using our API to drive the dashboard, it’s easy for us to keep everything in sync if we make changes to the API. And we wanted to make it easy for our customers to do the same.
We started out with ReadMe, which is an excellent industry standard. That let us get our documents published and dynamic. For further refinements, we went to Swagger/OpenAPI. We liked it because:
- It’s a well-known and widely-used format
- It allows us to generate usable code snippets and examples in many languages automatically
- It’s easy to add context and documentation to as we go.
- We can host it on readme.io or other places, depending on our traffic needs.
We created our REST specification using OpenAPI, and you can find our documents here: LaunchDarkly OpenAPI.
We’re still working on adding examples, descriptions, and context, but we think that the documentation is stronger and more usable already.
As always, if you have any comments, you can contact us here, or make comments directly in the repository.
I’ve updated some links and tweaked a few sentences since this was first published.