Stoplight Reviews & Product Details - Page 29

The organization of endpoints and models, as well as the online documentation. Review collected by and hosted on G2.com.

Sometimes I get confused trying to find a model that I mistenkenly saved on shared objects. There could be a confirm message before this kind of action (something like: do you really want to share this model?) Review collected by and hosted on G2.com.

The collaborative OAS API design features of Stoplight have be extremely valuable in prompting our team to address API deficiencies for several of our services. Teams can be formed and assigned to specific APIs being developed for the organization. The tool itself has enabled our teams to address missing or deficient APIs for several services, and to do so in an OAS compliant way. In most cases, the services were pre-existing but had no (or limited) API. Stoplight promoted fast, low man-hour on-boarding of developers and subsequent API design to address the deficiencies. In the case of a newly added service, Stoplight enabled the team to take an API-first approach, which heretofore has been rare for us and likely wouldn't have happened--or not with sufficient clarity and formalism--without Stoplight. Our group is small, with developers generally responsible for most phases of software development of their assigned projects and few formal processes. The incorporation of Stoplight into what development processes do exist was met very positively and did not come with high on-boarding or opportunity costs, which was a vital key requirement. The use of Stoplight put greater emphasis on API design ahead of implementation, permitting it to be better planned, in some cases reviewed, contributed to by other team members, and to be implemented slightly faster and with greater scope that would have been achieved otherwise. Review collected by and hosted on G2.com.

Like some others, we also were on-boarded to a beta Stoplight Next which caused a few issues initially. However, because this coincided with team members needing to fill knowledge gaps with respect to OAS, the effect of these issues was minor. Currently we have having more issues with documentation (and OAS spec, available via API) publication and presenting the documentation in a pleasing manner. This too may reflect our unfamiliarity with the capabilities, or may reflect constraints in Stoplight's documentation production; we're not sure yet. Additionally, we have need for non-OAS API documentation, although this may be out of scope for Stoplight. Review collected by and hosted on G2.com.

After evaluating several products to document multiple REST APIs - Postman, Swagger, API Blueprint and the main differentiator for me were:

- the ability to mix OAS-style documentation and Markdown pages, giving a one-stop tool to write the entire API documentation.

- a nice editor for the OAS doc, which offers both a UI and a way to edit JSON data directly

The team was very responsive to questions during the trial, and after becoming a paying customer. They've also been open to my feature requests as well.

The new version (Next) has evolved nicely since its launch a few month ago. Review collected by and hosted on G2.com.

I started using StopLight as Next was in beta. I hit a couple of minor issues but the team was responsive in addressing them and I've not encountered issues for weeks. Review collected by and hosted on G2.com.

The ability to contribute with a number of people to the same specification. Which is translated to oas under the hood. The ease of defining models and tests in the tool. Automatically publish documentation to html... Review collected by and hosted on G2.com.

The same user within multiple organisations, is billed in each organisation.. within our company we use stoplight for all our clients but when the client wants to contribute we need to create a project in a separate organisation (in this way the client can't see the other projects of other clients). The drawback is that each user at our side is billed for every organisation.. Review collected by and hosted on G2.com.

I love how accessible Stoplight is to everyone in our organization. It has become an essential tool for planning and organizing our API - a tool that even non-technical people understand and grasp.

I also love the hosted documentation - it fast and stable. Review collected by and hosted on G2.com.

I come into Stoplight really used to the OpenAPI (swagger) spec. Sometimes it is really difficult to figure out how to do something with Stoplight that I already know how to do in the OpenAPI spec. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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 when had unsaved changes, Stoplight wouldn’t make me aware of that, and then I’d lose my work (This is fixed now). Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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 huge time saver. Review collected by and hosted on G2.com.

The simplicity when sharing API specs with coworkers and allowing all of users to change those specs. The generated documentation is another positive feature. Finally the fact that we can still edit the code spec directly when in some cases where we can just copy from another location. Review collected by and hosted on G2.com.

Hard to use versioning. A killer feature would be change history, even if just locally. Review collected by and hosted on G2.com.

Organization of UI, mocking, out of the box usage, etc Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

We are on an older version of Stoplight and haven't gotten around to switching to the new version. Review collected by and hosted on G2.com.