Stoplight Reviews in January 2025: User Ratings, Pros & Cons

Excellent API documentation for our platform

What do you like best? The ability for us to quickly build out our internal API documentation for developer consumption. What do you dislike? Sometimes the UI can be slightly buggy (especially when adding nested pages. What problems are you solving with the product? What benefits have you realized? We now have an efficient and reliable method of distributing API documentation throughout our development team.

Great useful product

What do you like best? Easy to use interface and REST api mocking What do you dislike? new stoplight did not auto migrate my old project What problems are you solving with the product? What benefits have you realized? developer documentation and intra project communication

Swagger made easy!

What do you like best? Swagger made easy, finally - no excuses now not to fully document APIs. UI is intuitive, no tutorials necessary. Haven't found a case that Stoplight documentation couldn't cover What do you dislike? There are some bugs with having to save a new definition before being able to update them. What problems are you solving with the product? What benefits have you realized? - Massively accelerates development, as it makes it so much faster for API developers to ...

Stoplight generates great API docs and support is great

What do you like best? We went with Stoplight for the multi-language code generator. The developers love it. What do you dislike? No major issues. OpenAPI is complicated and Stoplight does a good job of making it easy to work with. What problems are you solving with the product? What benefits have you realized? It generates extremely useful interactive documentation from our Swagger JSON with minimal time and effort on our part.

Stoplight makes documenting any REST API a lot easier.

What do you like best? Stoplight's rich set of features allows for editing by means of a GUI as well as integration in a GitHub-driven process (as in our case). The docs look a lot cleaner than before and the HTTP request maker gives our docs a component of interactivity. Also, the support team has been really helpful so far. What do you dislike? Nothing really to be disliked comes to mind, but of course, Stoplight being a work in progress, there are some features that are not quite ...

Stoplight generates great API docs and support is great

What do you like best? We went with Stoplight for the multi-language code generator. The developers love it. What do you dislike? No major issues. OpenAPI is complicated and Stoplight does a good job of making it easy to work with. What problems are you solving with the product? What benefits have you realized? It generates extremely useful interactive documentation from our Swagger JSON with minimal time and effort on our part.

Friendly GUI for API first developement

What do you like best? As a Technical writer I need a friendly tool, with an easy-to-use interface so I can better collaborate with the development teams in the development and review of the documentation of our APIs. Its integration with Git allows teams to collaborative in a coordinated way. What do you dislike? Stoplight seems to be an immature tool yet, so now and them I stumble upon errors, or I miss things that I think should be there already. For example, I’ve noticed than ...

Great minus versioning

What do you like best? Organization of UI, mocking, out of the box usage, etc What do you dislike? Versioning/commits is strange/weird. Not any documentation out there. Not a clear way to have current vs WIP branches of API design. Got a peek at Stoplight Next and was excited about things that appeared there but no documentation for that I could easily find so we were scared to make the jump. Recommendations to others considering the product: Learn swagger stuff first to understand ...

Great tool for documentation

What do you like best? Very easy to create documentation for your API, you can customize it with a JSON look or use the tool, it also have a wide range of options to create the documentation and to visualize the data, What do you dislike? The test tool sometimes doesn't seem to work well, and it can be a little difficult to create a new register for new functionalities in the API. What problems are you solving with the product? What benefits have you realized? Documentation for APIs

Great minus versioning

What do you like best? Organization of UI, mocking, out of the box usage, etc What do you dislike? Versioning/commits is strange/weird. Not any documentation out there. Not a clear way to have current vs WIP branches of API design. Got a peek at Stoplight Next and was excited about things that appeared there but no documentation for that I could easily find so we were scared to make the jump. Recommendations to others considering the product: Learn swagger stuff first to ...