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

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

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 ...

Great tool for API design, composition, documentation

What do you like best? The ability to quickly add and manipulate elements with the designer, but still have the ability to make changes directly to the JSON data. Additionally, the ability to work with all projects through git makes coloring outside the lines possible. What do you dislike? I'd like to be able to use YAML editing, have the ability to segment versions so that say v1.1 is published, but those with sufficient authorization could access v1.2 that's in development. ...

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 ...

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, which ...

Great tool for API design, composition, documentation

What do you like best? The ability to quickly add and manipulate elements with the designer, but still have the ability to make changes directly to the JSON data. Additionally, the ability to work with all projects through git makes coloring outside the lines possible. What do you dislike? I'd like to be able to use YAML editing, have the ability to segment versions so that say v1.1 is published, but those with sufficient authorization could access v1.2 that's in development. Also, ...

Great spec-first enablement

What do you like best? Designing an API is extremely intuitive and simple. Mock testing is easy to configure. We are enabling concurrent front-end and back-end development to an agreed upon contract defined in Stoplight. What do you dislike? Management of common models and responses across projects. In a microservices world we are defining many stoplight projects, however, there are common elements that we would like to share between those projects. Making this more seamless would be a ...

Have been very pleased with stoplight and it's ease of use and features

What do you like best? The workspaces and the hosted docs and reloads What do you dislike? exporting OAS and having to pull out all the stoplight specific code Recommendations to others considering the product: Ease of use, rapid API development, good looking docs What problems are you solving with the product? What benefits have you realized? API development. It is helpful for me to start the development architecture through the APIs at first. Very rapid API prototyping, less ...

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) ...

Great spec-first enablement

What do you like best? Designing an API is extremely intuitive and simple. Mock testing is easy to configure. We are enabling concurrent front-end and back-end development to an agreed upon contract defined in Stoplight. What do you dislike? Management of common models and responses across projects. In a microservices world we are defining many stoplight projects, however, there are common elements that we would like to share between those projects. Making this more seamless would ...