API Linting is an excellent practice that fits into a Design-First approach: it helps save a lot of time when verifying your definition files. @philsturgeon has put together a guide on vacuum (@daveshanley): one of the best linters on the market.

It’s often better with a diagram! We’ve just added #mermaid support to allowing you to include diagrams and flowcharts directly in your documentation to make your #API easier to understand and adopt. More details here:.

Released some time ago, our API Design-first guide has just been updated. @philsturgeon revisits the relevance of this workflow, showing how it simplifies life for everyone throughout the #API lifecycle.

With @speakeasydev, we firmly believe that #OpenAPI is often a game-changer, and the support for Overlays reinforces this idea. We published a guide on this topic, showing how to generate your SDKs and retrieve custom code examples for your API doc.

For the world of APIs, 2024 was an exciting year full of innovations. And for us, it was just as eventful: beyond the features we deployed, we worked hard to make the use of documentation more seamless than ever. Here's a behind-the-scenes look.

For the beta release of our API Explorer, Yoan, our Product Manager/Designer, has prepared a live demo of this exciting new feature. Discover our vision and approach to this major addition to .

New year, new major feature! @scharrier, our CEO, introduces what we’ve been working on over the past few months:.

For the final day of #apidays Paris, and to meet popular demand, we’re sharing the latest batch of our famous cookies (the recipe is a closely guarded secret by one of our own) at our booth. Stop by to grab one, say hello, and chat a bit about APIs while you’re at it!.

RT @lbroudoux: @bump_hq @microcksio @YadaYac @philsturgeon 🎉 So happy this collaboration came to life finally! @bump_hq and @microcksio wor….

RT @microcksio: 🚀 Exciting news! @bump_hq & @microcksio are teaming up to revolutionize how you work with API specifications! 🔧✨. 👉 https:/….

How #OpenAPI adoption transforms your organization? This is the question that @scharrier, CEO of will (skillfully) address at #apidays Paris at 4:45 PM (room Aubépine 4). Between us, we’ve seen the teaser, and it promises to be fantastic. 👀.

The 2nd day of #apidays Paris has something a bit special. #OpenAPI and #AsyncAPI cheat sheets are still available in printed versions at our booth. And it’s the chance to attend the talk by @scharrier, our CEO: How OpenAPI adoption transforms your organization at 4:45 PM.

.@microcksio and Bump rely on the same source of truth to provide you with the best API lifecycle services: the specification file. From this file, you can test, mock, and document your APIs to prepare for their release. @YadaYac @lbroudoux @philsturgeon .

Two months after the very first OpenAPI cheat sheet, we’re excited to share our version for AsyncAPI with the community. Take a look, it’s now yours and, of course, open to your feedback! Bonus: printed copies are available at our booth at apidays Paris!.

We are absolutely thrilled and proud to announce the arrival of Laura Adao, who joins us as an Account Executive. If you’re attending apidays Paris in the coming days, don’t hesitate to stop by and say hello to her (and to us too—the whole team will be there)!

🔍 Nearly 40% of developers say inconsistent API docs are their biggest integration hurdle (2024 State of the API Report). Embrace a spec-first approach to create a single source of truth, strengthen partnerships and drive success. 🚀 - by @DoerrfeldBill .

After a long preparation process, your #API is live, and its #documentation is finally published. But this is just the beginning: discover how to improve your API by gathering user feedback with this guide by @philsturgeon.

BigID is a data intelligence platform that helps organizations manage sensitive data, enhancing privacy, security, compliance, and data governance. Switching their API doc to increased their doc readers’ satisfaction by nearly 90%.

Have you decided (or are about to decide) to use discriminators in your OpenAPI specification? It might not be the best choice—find out why, by @philsturgeon.

To everyone who thinks they don’t have time to write (API) documentation, to those who assume it’s a problem for your future self, @philsturgeon and we dedicate this article to you: