Stoplight Reviews in July 2026: User Ratings, Pros & Cons

Minimize Impact

What do you like best? Design and mock APIs at ease. There are many features of this product ranging from design, testing, documenting, and publishing that makes it appealing to many API designers who need to communicate all aspects of evolving an API product. What do you dislike? Design view can be presented better. I like the Read-only view but sometimes when toggling from Read to Design mode, the API endpoints are not grouped in the same way as the Read view so it makes it harder ...

Minimize Impact

What do you like best? Design and mock APIs at ease. There are many features of this product ranging from design, testing, documenting, and publishing that makes it appealing to many API designers who need to communicate all aspects of evolving an API product. What do you dislike? Design view can be presented better. I like the Read-only view but sometimes when toggling from Read to Design mode, the API endpoints are not grouped in the same way as the Read view so it makes it harder to ...

A powerful tool in general but still quite a few things to improve

What do you like best? The flexibility of defining API docs, tests and all relevant API stuffs in one single container, which makes it a powerful tool to use and it greatly addresses our e2e needs for API development. The designer mode is also my favorite, from which non-technical staffs could easily gain information. What do you dislike? Stoplight being a new tool and start-up company, many times I find the documentation is lagging behind and we would have to approach product ...

Stoplight makes it easy to create api docs

What do you like best? - Simple to use - Can create tables, pictures to explain the api better to the client -> Visual OpenAPI Designer was added - Can test api with moc server What do you dislike? - No easy way to transfer a word documentation into stoplight - Not sure how we can check if the api doc is stoplight is in sync with the api - Not many tutorials on youtube - I wish there would be a better way to save the api doc as a microsoft word document (.doc - I ...

Stoplight review

What do you like best? Easy editing Intuitive interface Supports both Yml and Jain version of OAS 2 What do you dislike? Lack of support for OAS 3.0 Ability to export models in other formats like Avro What problems are you solving with the product? What benefits have you realized? API definions in OAS

Stoplight review

What do you like best? Easy editing Intuitive interface Supports both Yml and Jain version of OAS 2 What do you dislike? Lack of support for OAS 3.0 Ability to export models in other formats like Avro What problems are you solving with the product? What benefits have you realized? API definions in OAS

Great product potential, missing some main features.

What do you like best? I like how we can use the api to change endpoints when we change them. Illuminating manual work. What do you dislike? That in Next, you cannot have nested menu's. I also dis-like how it's linked to Github, but you can't open a PR against any page. Recommendations to others considering the product: Stick with classic until Next has more features. It is missing simple things like nested menu's and allowing some endpoints to be private. What problems are you ...

Great software to enable API Design and Documentation

What do you like best? Stoplight has a great interface for API design, documentation and then automatically generating a swagger spec. The service is great and the team is responsive to feedback. What do you dislike? We are on an older version of Stoplight and haven't gotten around to switching to the new version. What problems are you solving with the product? What benefits have you realized? Rapid, consistent API development and documentation.

Best was to build models and routes and publish documentation

What do you like best? Multiple editing modes for the models and routes. Can use the UI or direct JSON schema editing in JSON. The self-publishing documentation is invaluable to easily sharing information with your team or even for public consumption. What do you dislike? The "next" (current) UI doesn't seem as good as the Legacy version, however, I haven't played with it enough to be more thorough in detail for it. I DO wish there was a way to "upgrade" (without Swagger import, ...

The best experience I had documenting APIs.

What do you like best? The JSON Schema editors, the imports and the tutorial editor with playable examples. What do you dislike? Lack of GraphQL support (playground in examples, as far as I know). Lack of an easy way to document multiple APIs with different access levels and sharing resources and schemas. What problems are you solving with the product? What benefits have you realized? API Documentation