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

The best OAS tool I've found

What do you like best? Stoplight is becoming an essential tool for us as we develop our API's. Stoplight makes designing and creating Swagger / OAS definition files really easy. What do you dislike? The UI of "next" version is a bit hard to get used to. It would be nice if I could group endpoints together when I am designing them like was possible in the previous version. What problems are you solving with the product? What benefits have you realized? Stoplight helps us ...

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.

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.

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

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

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