Runscope's company blog covering API testing and monitoring, API design advice, engineering notes, and its acquisition by CA Technologies.
HN users link it for API error and GraphQL-alternative posts. One commenter is fairly happy with Runscope for basic API monitoring but wants longer response data retention.
Runscope - San Francisco, CA
Runscope is building tools for developers working on API-driven mobile and web applications. Working at Runscope means joining a small team of fun, smart, collaborative people who care about quality, APIs, and building developer tools. Even if you don't see a position here that fits you perfectly, we're always interested in talking with people who love APIs. We have proven work/life balance (checkout https://www.runscope.com/work_at_runscope for the data), are well funded, and we're looking to grow the team!
We write code in Python and Go, deploy 15-20 times a day, and use our own product to help us write better code!
Positions open:
* Lead Web Engineer
* Mobile Networking Engineer
* Senior Software Engineer
* Software Engineer
* Enterprise Inside Sales
If you're interested or want more information email us at: buildthefuture@runscope.com
Check out the jobs page: https://www.runscope.com/work_at_runscope
Read some of our blog posts:
http://blog.runscope.com/posts/go-at-runscope
http://blog.runscope.com/posts/100-continue
http://blog.runscope.com/posts/introducing-runscope-radar-automated-api-testing-and-monitoring
"Everything is going to be 200 OK"
Seems like a useful tool; thanks for sharing it!
Two questions:
1) What's the diff logic? At first glance, it looks like JSON is reformatted (maybe canonicalized in some way) and then a line-by-line diff is applied. Is there more to it? Since the tool seems JSON-aware, I was surprised to see an added trailing comma up as a difference.
2) Do you have plans to expand the kind of HTTP requests users can make? It would be nice to use different verbs, headers, and request bodies. Runscope has a similar tool[0] built in that I believe (haven't tried it yet) allows a bit more flexibility, but it would be nice to have a standalone tool available.
[0] http://blog.runscope.com/posts/comparing-http-requests-using-runscope
Hey! I cover that a bit ni a followup blog post :)
https://blog.runscope.com/posts/you-might-not-need-graphql
tl;dr: maybe you want OData, JSON-API, or one of the many other standards or practices that solve this simple problem as their super-set of functionality on top of the networking principles of REST.
Using GraphQL for this alone is rather nuclear, as you gain a lot with GraphQL but lose other stuff.
We have been fairly happy with Runscope [0] for fairly simplistic monitoring of api response codes and body payloads. My biggest complaint is probably the lack of individualized response data after >= 24 hours.
Still waiting to see if the CA Technologies acquisition [1] makes things worse or not.
[0] https://www.runscope.com/
[1] https://blog.runscope.com/posts/301
https://www.runscope.com/docs/request-capture paired with https://www.runscope.com/docs/api/messages can do that.
Or use http://blog.runscope.com/posts/monitor-your-webhook-workflows-with-new-incoming-requests-for-api-tests