StopLight for all your API testing needs
May 31, 2019

StopLight for all your API testing needs

Anonymous | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User

Overall Satisfaction with StopLight

At our organization, StopLight is being used to test, debug, and share our web APIs internally with other departments and teams. It's not used exclusively, but on a team-by team basis across several departments. We use it mainly for testing, like for OAI and RAML code for testing our endpoints.
  • OAI code. StopLight is a great tool to use if you use Swagger for testing your endpoints.
  • Sharing API's. StopLight makes it easy for us to share our API's internally with other teams.
  • Tech support. StopLight's dev team responds quickly and helpfully to tech questions and there's plenty of forum support to boot.
  • Simplicity of set up. Although it's not difficult, there are tools out there that are easier to set up for testing endpoints.
  • Again, it's perfectly functional, but some competitors I think have a more user friendly UI to them.
  • Increased efficiency
  • Improved API reliability
  • Easier testing
I'd like to also throw Runscope and Fiddler into the mix. Between StopLight and all these competitors, we've chosen StopLight primarily for the support, ease of use, and reliability. Most tools out there today are top-notch, so it really comes down to personal preference and different use-cases. Having used other API testing frameworks, StopLight definitely stacks up against the competition.
API mocking, testing, and sharing are all built in functions for StopLight that work quite well. They even have functionality for generating OAI and RAML code as well, which is a huge plus. AS for as areas where StopLight is not appropriate, if you're doing anything other than API testing, StopLight may not be appropriate for use.

Stoplight Feature Ratings