#Insomnia api testing how to
#Insomnia api testing skin

As well as all this, it quietly sorts all the headers out, so that everything just works. The schema is then used to populate the auto-complete system, which makes composing queries very quick indeed. By selecting GraphQL as the body type in the drop down, Insomnia will immediately go and fetch the schema from the endpoint. The first difference to highlight is obviously the one that drew me to Insomnia вЂ“ GraphQL support. And both have ways of taking data from the response of one request and using it in another (via вЂњ test scriptsвЂќ in Postman and вЂњ chainingвЂќ in Insomnia).

Both have templating/tagging systems that allow for the management of multiple environments.TheyвЂ™re both вЂњfreemiumвЂќ apps, with extra features (mainly around collaboration) available for subscribers.Both are Electron apps, with the usual pros (e.g.

#Insomnia api testing skin

The similarities are more than skin deep too:

#Insomnia api testing how to

Regardless, both make it pretty obvious how to write and run your first call. To my eye, Insomnia is almost a little stark when you first run it, but I suppose this plays to the simplicity of the aesthetic. Postman arranges these panes one above the other, but Insomnia defaults to placing them side by side. The similaritiesД®ven at first glance, there are a few similarities between the two: both have a panel on the left for saved requests, a pane for writing composing requests, and a pane for the response. The Insomnia app running a simple GraphQL query against the (wonderful) FakerQL hosted endpoint. Anyway, with that disclaimer out of the way, letвЂ™s get stuck in. IвЂ™ll try and do a comparison but I may well miss some things.

Now, IвЂ™m not an expert in either application, but IвЂ™ve been using Postman for a while now and IвЂ™ve used Insomnia quite a bit this week. When I Googled for tips on using Postman for GraphQL, the top result was this Stackoverflow answer, which had been edited to recommend Insomnia. Since GraphQL queries are just REST calls with a specific payload, it is, of course, entirely possible to perform them in Postman. Recently, however, IвЂ™ve changed jobs and started working extensively with GraphQL (a topic on which I may in time write a post). The truth is that I have been really happy with Postman on the whole. Unlike last time, however, I wonвЂ™t be ditching the previous flavour of the monthвЂ¦ Read on to discover why (for the time being at least) they both get a spot on my desktop.ДЇirst things first, itвЂ™s probably worth explaining what lead me to even look for an alternative to Postman. Before that, IвЂ™d been using Fiddler to make calls to REST APIs and man, was that a drag! Recently IвЂ™ve had a similar experience when I discovered an alternative REST client called Insomnia. Just over a year ago I was emphatically singing the praises of Postman.