verb VS restclient.el

plz-see: Interactive HTTP client, similar to restclient and verb, but using Elisp instead of a special text-based syntax.

Ah, btw. I just realized, verb's verb-send-request-on-point doesn't always properly work with source blocks. So I pushed a fix, PR is here.

have you checked this https://github.com/federicotdn/verb . Its emacs package and i am able to write and test api's with text files.

Not as usable for testing, but verb.el[1] is a great tool for doing something very similar in org-mode

[1] https://github.com/federicotdn/verb

I've been a long time user of the org-mode code blocks feature—storing runnable code block inline in the document. Something I've recently started using is verb to include HTTP requests in my documents when I'm testing out web APIs.

Looks also interesting, but it doesn't fit my use cases: I need custom functions to grab values/data from other sources (e.g. pocket-reader.el).restclient` is more about having pre-defined HTTP requests (path, headers, payload etc.) in a buffer and a major mode for executing the requests. Pretty much the same what verb offers.

There is also verb.el.

plz-see: Interactive HTTP client, similar to restclient and verb, but using Elisp instead of a special text-based syntax.

There's a great Emacs mode, and it looks like it works in the same way, putting it in a file:

https://github.com/pashky/restclient.el

Emacs enthusiasts have https://github.com/pashky/restclient.el

I see some parallels to Hurl, but having everything inside Emacs is hard to beat, just thinking about using M-x jq-interactivly for json responses ...

I recently switch from custom Bash wrappers around curl to restclient.el [1]. It has similar features. Especially nice is the integration with jq for fetching specific data (or inspection of results with jq-mode). And, whoever is inclined to appreciate it, the fact that I can stay within Emacs. No need to get familiar with a new UI/UX.

[1]: https://github.com/pashky/restclient.el