Show HN: Stoplight – Visual API Tooling
stoplight.io
stoplight.io
This means businesses can develop their best API by making it accessible to everyone. Ultimately this saves large companies a lot of time and money, and improves the user experience.
We're also launching API Docs today, it's hosted API documentation for every OAI (Swagger) and RAML spec out there.
I'd love to get your feedback on Stoplight, and answer any questions you might have!
Second impression is that it seems like a Swagger Editor tool combined with a REST Explorer (like Postman or Advanced REST Client). Testing now and will update with some more thoughts :)
The hosted documentation integration is completely free - we have a paid option coming soon, that adds custom domains, theming, analytics, etc.
Eager to hear what you think - let us know!
Some feedback:
- The left hand menu for API, versions, documentation (or something) totally confuses me. Even after thinking about it for multiple minutes I don't really get it. I think there are multiple things being represented by the same interface type, but I'm not sure.
- Sometimes action buttons on top, action buttons on the bottom.
- Prism... where is it? Why does the main interface change when I switch from "hosted" to "local"? What does "local" actually mean?
You have a really nice tool, but for now it was too complicated for me :/ Some UI and usability love would probably help quite a lot.
Prism processes the traffic that passes through it, and generates your spec code from that. It can identify dynamic parameters in the url, build json schemas, etc.
Here's a little post + video we put together: https://medium.com/oh-what-a-wonderful-web/how-to-generate-2...
And another, demonstrating a slightly different process of generating spec code from the Peach mobile app API traffic:
Any thoughts on import from Apiary/Blueprint?
FYI if you haven't clicked on the animation on homepage, do it...it's addicting
From the API Designer (which is private), you can optionally publish any of your API versions out to api-docs.io, for public consumption. You don't even need to publish your entire API definition out - you can mark which endpoints/models are private versus public. Only the parts of your internal docs marked as public will be published out :).
Also, I define the OAuth2 security in the version, but it shows up nowhere else except for the exports. It would be nice if you define which resources are secured by what. For instance all of my resources require apikey as well as an OAuth2 token.
In the "settings" tab for each endpoint, you can mark which security schemes apply to the endpoint. It's kind of hidden, we're moving it to the general definition tab. Also, that info will be exposed in api-docs (which security schemes an endpoint requires/supports) in an update later this week!
They blogged about their experience so far with our tools here: https://sendgrid.com/blog/using-a-prototype-as-an-api-produc...