Looking for something?

Dev tip: Use Requestbin for easy analysis and debugging when developing your webhooks, connectors, API's and applications

Lately there’s been an explosion on popularity of webhooks and integration with various services I’m using. It’s a great way to develop integration points for services, and we can see this with Office 365 Groups and their Connectors, Slack and their Integrations, Azure Logic Apps Connectors and so on. 

You have tools like Fiddler, Advanced REST Client for Chrome and Postman for Chrome which does a great job with analyzing request flows and data on the clients. However, one thing I was missing was the ability to easily (and I mean 1-2-3 easy) analyze and measure the requests my deployed API’s or webhooks were doing. It isn’t always you can analyze it using a client-side analyzer since the request may happen from anywhere and at any time with webhooks, for example.

Quick tip: Try requestb.in

During my recent development projects for various integrations and hooks, I’ve stumbled upon Requestb.in, which is a way to easily log and monitor your API usage. Consider this post just a tip for using requestbin – see the link on the Azure Documentation below for an example of how to use it.

Since there’s already a lot of posts out there on how to actually use Requestbin, I’ll just point to one which is building an Azure App Service API app trigger, and uses Requestbin to help out during dev:


Happy coding.

0 Comments 04 January 2016
Tobias Zimmergren

Tobias Zimmergren

Hi, I'm Tobias Zimmergren. I am a Microsoft MVP for SharePoint and I use this site to share my thoughts on tech with you on topics like SharePoint, Office 365, Azure and general web development.

  Malmö, Sweden

Related Post

Comments powered by Disqus

Sign up to my e-mail newsletter to get news about Azure, SharePoint and Office 365 and get instant notifications when I publish new posts!

Enter valid email